Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 21 Dec 2023 17:26:48 +0100 | Subject | Re: [PATCH] scripts/kernel-doc: restore warning for Excess struct/union | From | Vegard Nossum <> |
| |
On 21/12/2023 16:20, Jonathan Corbet wrote: > It's mostly done; I've gotten it down to under 200 and sent patches to > make the changes. Randy is working on it too, I know. It's not always > just deletion, but the fixes are usually pretty straightforward.
Ah, cool. Will leave it to you, then.
>> 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). > > I suppose, but how do you know you've properly addressed the warning if > you don't do a build afterward? I don't see that saving a whole lot of > effort, but maybe I'm missing something?
You would definitely have to do local builds too, it's just about raising awareness of remaining issues and lowering the barrier for drive-by contributors to picking something to work on. I can only speak for myself but I find it easier to go look at a list of known problems than initiating a docs build and waiting for it to come back.
Syzbot has monthly per-subsystem reports now (since ~March, AFAICT):
https://lore.kernel.org/all/0000000000007fbf7a060cc67998@google.com/
A monthly email is maybe even better than what I suggested.
Anyway, I'll try something out, we can see how it works.
Vegard
| ![\](/images/icornerr.gif) |