From: Stephan Mueller <smueller@chronox.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc: crypto: warning cleanup
Date: Mon, 24 Aug 2015 06:51:35 +0200 [thread overview]
Message-ID: <5137031.WPPXXLuRMs@tauon.atsec.com> (raw)
In-Reply-To: <20150823135101.270c6630@xps.lwn.net>
Am Sonntag, 23. August 2015, 13:51:01 schrieb Jonathan Corbet:
Hi Jonathan,
>Fix up a missing field description and a misdirected doc inclusion to make
>a couple of warnings go away.
>
>Signed-off-by: Jonathan Corbet <corbet@lwn.net>
>---
> Documentation/DocBook/crypto-API.tmpl | 2 +-
> include/crypto/aead.h | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
>diff --git a/Documentation/DocBook/crypto-API.tmpl
>b/Documentation/DocBook/crypto-API.tmpl index 0992531ffefb..980bcc994913
>100644
>--- a/Documentation/DocBook/crypto-API.tmpl
>+++ b/Documentation/DocBook/crypto-API.tmpl
>@@ -1687,7 +1687,7 @@ read(opfd, out, outlen);
> !Pinclude/linux/crypto.h Block Cipher Algorithm Definitions
> !Finclude/linux/crypto.h crypto_alg
> !Finclude/linux/crypto.h ablkcipher_alg
>-!Finclude/linux/crypto.h aead_alg
>+!Finclude/crypto/aead.h aead_alg
This one is already in the cryptodev-2.6 kernel.
>From now on, I will always CC the linux-doc mailing list on patches pertaining
the crypto documentation so that you can see the patches too.
> !Finclude/linux/crypto.h blkcipher_alg
> !Finclude/linux/crypto.h cipher_alg
> !Finclude/crypto/rng.h rng_alg
>diff --git a/include/crypto/aead.h b/include/crypto/aead.h
>index 7169ad04acc0..88c6cdf3a886 100644
>--- a/include/crypto/aead.h
>+++ b/include/crypto/aead.h
>@@ -120,6 +120,7 @@ struct aead_givcrypt_request {
> * @exit: Deinitialize the cryptographic transformation object. This is a
> * counterpart to @init, used to remove various changes set in
> * @init.
>+ * @base: Common crypto API algorithm data structure
I am wondering: does this really fix the issue? I tried it and it failed (i.e.
still produced errors by the parser) due to the exotic definition in of this
variable in the C code.
> *
> * All fields except @ivsize is mandatory and must be filled.
> */
Ciao
Stephan
next prev parent reply other threads:[~2015-08-24 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 19:51 [PATCH] doc: crypto: warning cleanup Jonathan Corbet
2015-08-24 4:51 ` Stephan Mueller [this message]
2015-08-24 8:03 ` Jonathan Corbet
2015-08-24 13:30 ` Stephan Mueller
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=5137031.WPPXXLuRMs@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=corbet@lwn.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@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