Re: [PATCH v3 00/17] bcache for 4.19, 3rd wave
On 2018/8/12 5:42 AM, Jens Axboe wrote: > On 8/10/18 11:19 PM, Coly Li wrote: >> Hi Jens, >> >> This series contains several minor fixes and code cleanup reported by >> scripts/checkpatch.pl. After this series, there are still a few warning >> from checkpatch.pl, but I think they are necessary to be the way they >> are and don't change them. For example, error message exceeds 80 chars >> line limit. > > It's a little late to apply these at this point, since 4.18 will be > released tomorrow. I can queue them up for later in the merge > window, for a post pull. > Hi Jens Sure, thank you. Coly Li
Re: [PATCH v3 00/17] bcache for 4.19, 3rd wave
On 8/10/18 11:19 PM, Coly Li wrote: > Hi Jens, > > This series contains several minor fixes and code cleanup reported by > scripts/checkpatch.pl. After this series, there are still a few warning > from checkpatch.pl, but I think they are necessary to be the way they > are and don't change them. For example, error message exceeds 80 chars > line limit. It's a little late to apply these at this point, since 4.18 will be released tomorrow. I can queue them up for later in the merge window, for a post pull. -- Jens Axboe
Re: [PATCH] blkcg: Make blkg_root_lookup() work for queues in bypass mode
On 8/10/18 2:28 PM, Bart Van Assche wrote: > For legacy queues the only call of blkg_root_lookup() happens after > bypass mode has been enabled. Since blkg_lookup() returns NULL for > queues in bypass mode, modify the blkg_root_lookup() such that it > no longer depends on bypass mode. Rename the function into > blk_queue_root_blkg() as suggested by Tejun. Applied, thanks. -- Jens Axboe
