On Wed, May 03 2017 at 1:51pm -0400, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Tue, May 2, 2017 at 11:58 AM, Mike Snitzer <snitzer@xxxxxxxxxx> wrote: > > > > - Add a new DM integrity target that emulates a block device that has > > additional per-sector tags that can be used for storing integrity > > information. > > So this one comes with a nice documentation file and everything, but > let me just quote all the help that you give users when faced with the > CONFIG_DM_INTEGRITY choice: > > CONFIG_DM_INTEGRITY: > > This is the integrity target. > > That's it. Not really very helpful. > > The kernel configuration phase is already likely the most frustrating > part of building your own kernel, it's really worth trying to make it > a *bit* less frustrating than this. > > Even just a stupid little blurb that says > > "Emulates a block device that has additional per-sector tags that can > be used for storing integrity information. > > If you're not sure, you can probably just say 'n'" > > or something like that. People who use this likely know they use it, > and it should lower the stress level for others. Sure thing. Sorry for it being so terse. I'll get it fixed and send it your way end of this week or early next (waiting on a dm-cache fix from Joe Thornber that I'll send at the same time). Thanks, Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
