On 15/12/2023 17:28, Jonathan Corbet wrote:
*sigh* This adds nearly 600 new warnings. Anybody gonna help fix them?
I think in the vast majority of the cases the fix will be to just remove the offending line from the kerneldoc, so it's not particularly difficult, mostly just overhead from the patch preparation/submission process. I'd be happy to take a stab at it -- I think we could even script most of it. Respond here, I guess, if anybody else wants to do some so we can split it up. On a related note, it might be useful to have some kind of "status page" somewhere on the web for the docs where you can see a list of unresolved documentation warnings in mainline/docs-next/next without having to do a local build first (as a way to solicit contributions). Vegard
