From: Randy Dunlap <rdunlap@infradead•org>
To: Jonathan Corbet <corbet@lwn•net>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the jc_docs tree
Date: Tue, 19 Dec 2023 15:59:58 -0800 [thread overview]
Message-ID: <4cbcd213-55f9-4525-8be0-29db00a468d2@infradead.org> (raw)
In-Reply-To: <87r0jjmw59.fsf@meer.lwn.net>
On 12/18/23 06:18, Jonathan Corbet wrote:
> Stephen Rothwell <sfr@canb•auug.org.au> writes:
>
>> Hi all,
>>
>> After merging the jc_docs tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> include/crypto/hash.h:248: warning: Excess struct member 'digestsize' description in 'shash_alg'
>>
>> and 636 new similar warnings :-(
>>
>> Exposed by commit
>>
>> b77fdd6a48e6 ("scripts/kernel-doc: restore warning for Excess struct/union")
>>
>> I am not sure what we should do about this ... last Friday I only
>> got about 18 lines of warnings.
>
> The warnings were expected, of course.
>
> The alternatives are to fix the docs or to revert b77fdd6a48e6,
> pretending that all those kerneldoc errors don't actually exist. The
> fixes should be pretty easy to do (and there's far less of them than it
> seems from the number of warnings). I can't get there right away but if
> nobody beats me to it I'll try to toss some patches together.
Hi Jon,
Attempt at a little coordination:
It looks like you are working on some net-related patches for this.
I am currently working on fs/ and kernel/ patches.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
next prev parent reply other threads:[~2023-12-19 23:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 7:28 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59 ` Randy Dunlap [this message]
2023-12-20 0:02 ` Jonathan Corbet
2023-12-20 0:04 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-07-30 0:29 Stephen Rothwell
2025-07-30 13:01 ` Jonathan Corbet
2025-07-30 14:30 ` Christophe Leroy
2025-07-30 15:14 ` Randy Dunlap
2025-07-30 14:31 ` Stephen Rothwell
2021-02-23 5:19 Stephen Rothwell
2021-01-13 4:14 Stephen Rothwell
2021-01-13 4:12 Stephen Rothwell
2021-01-13 4:18 ` Stephen Rothwell
2021-01-13 4:07 Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet
2021-01-21 2:07 ` 司延腾
2021-01-21 18:30 ` Jonathan Corbet
2020-12-07 7:52 Stephen Rothwell
2020-11-16 6:03 Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17 ` Jonathan Corbet
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=4cbcd213-55f9-4525-8be0-29db00a468d2@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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