public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Linux Crypto List <linux-crypto@vger.kernel.org>,
	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 libcrypto tree
Date: Thu, 6 Nov 2025 18:27:00 +1100	[thread overview]
Message-ID: <20251106182700.092a328f@canb.auug.org.au> (raw)
In-Reply-To: <20251106041953.GB1650@sol>

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]

Hi Eric,

On Wed, 5 Nov 2025 20:19:53 -0800 Eric Biggers <ebiggers@kernel.org> wrote:
>
> Okay, it's because some kernel-doc warnings were accidentally turned off
> for everyone :-(  And they just got turned back on by
> https://lore.kernel.org/r/20251104215502.1049817-1-andriy.shevchenko@linux.intel.com/
> With that applied, './scripts/kernel-doc -v -none include/crypto/sha3.h'
> does catch this.

Yeah, I found quite a few warnings today.

> I folded the following into "lib/crypto: sha3: Add SHA-3 support" to
> convert the comments starting with "/**" into proper kerneldoc comments:

Thanks.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-11-06  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  3:36 linux-next: build warning after merge of the libcrypto tree Stephen Rothwell
2025-11-06  3:55 ` Eric Biggers
2025-11-06  4:19   ` Eric Biggers
2025-11-06  7:27     ` Stephen Rothwell [this message]
2025-11-06  5:43   ` Randy Dunlap

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=20251106182700.092a328f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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