Re: [dm-devel] [PATCH v4 1/4] dm dust: report some message results back to user directly

2020-06-29 Thread yangerkun
Hi Mike, does there any advice for this patchset? Thanks, Kun. 在 2020/6/20 5:10, Bryan Gurney 写道: From: yangerkun From: yangerkun Some type of message(queryblock/countbadblocks/removebadblock) may better report results to user directly. Do it with DMEMIT. [Bryan: maintain __func__ output i

Re: [dm-devel] [PATCH v4 1/4] dm dust: report some message results back to user directly

2020-06-28 Thread Mike Snitzer
It is on the dm-devel patchwork list to pick up for the 5.9 merge window. I've just been busy with other work. Thanks, Mike On Sat, Jun 27 2020 at 9:08pm -0400, yangerkun wrote: > Hi Mike, does there any advice for this patchset? > > Thanks, > Kun. > > 在 2020/6/20 5:10, Bryan Gurney 写道: > >

Re: [dm-devel] [PATCH v4 1/4] dm dust: report some message results back to user directly

2020-06-22 Thread yangerkun
Hi, Thanks a lot for your fix and this patchset! It looks better than before! Thanks, Kun. 在 2020/6/20 5:10, Bryan Gurney 写道: From: yangerkun From: yangerkun Some type of message(queryblock/countbadblocks/removebadblock) may better report results to user directly. Do it with DMEMIT. [Brya

[dm-devel] [PATCH v4 1/4] dm dust: report some message results back to user directly

2020-06-19 Thread Bryan Gurney
From: yangerkun From: yangerkun Some type of message(queryblock/countbadblocks/removebadblock) may better report results to user directly. Do it with DMEMIT. [Bryan: maintain __func__ output in DMEMIT messages] Signed-off-by: yangerkun Signed-off-by: Bryan Gurney --- drivers/md/dm-dust.c |