On 17/11/16 18:23, Shaohua Li wrote: >> And yes, I *AM* volunteering to do the work - as I said elsewhere, I >> > want to put a load of kerneldoc into the raid source, and get to >> > understand it all, but the downside is you'll get a lot of newbie-ish >> > questions from me trying to get to grips with what's going on. I'm an >> > experienced C programmer but kernel style is alien to me - you know the >> > disconnect when you're reading something, you can read the words easily, >> > but you can't decipher the meaning. That's how I feel reading the kernel >> > source at the moment. >> > >> > Are we up for it? > Yep, that makes sense. the journal (current write-through mode and upcoming > write-back mode) does deserve a description. I'll add something into > Documentation dir in kernel source. >From what I can make out ... :-) The new kernel documentation system actually builds a load of stuff into the Documentation/output directory from the kernel source. In other words, it'll be far better edited into the source files. And/or put a .rst file in the md directory. I need to dig into this, and work out how it all fits together (I'm having trouble running it on my main system at the moment, gentoo takes forever to upgrade and the bits I need won't install ...) https://www.kernel.org/doc/ When you've written it up, post it to the list, and we'll see about getting it into the new documentation system rather than just dropping it into the Documentation directory (I think the new system will put it in Documentation/output/drivers/md, which is lot more sensible than just jumbled in Documentation along with everything else. Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
