From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] scripts/kernel-doc: restore warning for Excess struct/union
Date: Fri, 22 Dec 2023 16:54:13 -0700 [thread overview]
Message-ID: <87wmt56bfe.fsf@meer.lwn.net> (raw)
In-Reply-To: <b9165c65-0cbe-43f0-8634-361308a01972@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> On 12/21/23 07:20, Jonathan Corbet wrote:
>> Vegard Nossum <vegard.nossum@oracle.com> writes:
>>
>>> 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.
>>
>> 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.
>>
>
> I'm still seeing lots of Excess warnings from
> include/crypto/hash.h
> include/crypto/skcipher.h
> drivers/gpu/drm/* (several files there have warnings)
>
> I would be happy to see Vegard's help on this - unless Jon has already
> addressed those warnings.
Nope, I've not gone there and won't manage it before sometime next week
at best. I'd be delighted if somebody waded into those warnings.
Thanks,
jon
prev parent reply other threads:[~2023-12-22 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 7:02 [PATCH] scripts/kernel-doc: restore warning for Excess struct/union Randy Dunlap
2023-12-14 7:05 ` Randy Dunlap
2023-12-15 1:02 ` Kees Cook
2023-12-15 5:35 ` kernel test robot
2023-12-15 5:38 ` Randy Dunlap
2023-12-15 6:48 ` kernel test robot
2023-12-15 16:28 ` Jonathan Corbet
2023-12-21 13:48 ` Vegard Nossum
2023-12-21 15:20 ` Jonathan Corbet
2023-12-21 16:26 ` Vegard Nossum
2023-12-22 20:11 ` Randy Dunlap
2023-12-22 23:54 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmt56bfe.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=rdunlap@infradead.org \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).