public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Lukas Wunner <lukas@wunner.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org
Subject: Re: [PATCH cryptodev-2.6] crypto: doc - Fix akcipher title reference
Date: Thu, 10 Oct 2024 17:13:16 +0800	[thread overview]
Message-ID: <ZwearIUezhYVOvaQ@gondor.apana.org.au> (raw)
In-Reply-To: <89d99476b2b57bcd3e306996ec4a60db1706253f.1728378559.git.lukas@wunner.de>

On Tue, Oct 08, 2024 at 11:12:01AM +0200, Lukas Wunner wrote:
> Stephen reports a documentation build warning for "make htmldocs"
> introduced by recent commit 6b34562f0cfe ("crypto: akcipher - Drop
> sign/verify operations").
> 
> The commit renamed a paragraph title in a header file, but neglected to
> amend the title reference in the API documentation.  Fix it.
> 
> Fixes: 6b34562f0cfe ("crypto: akcipher - Drop sign/verify operations")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/all/20241008172926.0b995ea7@canb.auug.org.au/
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
> ---
>  Documentation/crypto/api-akcipher.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Patch applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2024-10-10  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  6:29 linux-next: build warning after merge of the crypto tree Stephen Rothwell
2024-10-08  9:12 ` [PATCH cryptodev-2.6] crypto: doc - Fix akcipher title reference Lukas Wunner
2024-10-10  9:13   ` Herbert Xu [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=ZwearIUezhYVOvaQ@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lukas@wunner.de \
    --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