From: Eric Biggers <ebiggers@kernel.org>
To: 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 crc tree
Date: Thu, 19 Jun 2025 11:38:16 -0700 [thread overview]
Message-ID: <20250619183816.GA100715@sol> (raw)
In-Reply-To: <20250611142832.1e151978@canb.auug.org.au>
On Wed, Jun 11, 2025 at 02:28:32PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the crc tree, today's linux-next build (htmldocs) produced
> this warning:
>
> lib/crc/crc32-main.c:1: warning: no structured comments found
>
> Introduced by commit
>
> 3eee6f3d771d ("lib/crc32: remove unused combination support")
>
> --
> Cheers,
> Stephen Rothwell
Fixed now, by
https://lore.kernel.org/r/20250619183414.100082-2-ebiggers@kernel.org/
- Eric
prev parent reply other threads:[~2025-06-19 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 4:28 linux-next: build warning after merge of the crc tree Stephen Rothwell
2025-06-19 18:38 ` Eric Biggers [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=20250619183816.GA100715@sol \
--to=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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