From: "Stephan Müller" <smueller@chronox.de>
To: Rabin Vincent <rabin.vincent@axis.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
Rabin Vincent <rabinv@axis.com>
Subject: Re: [PATCH] crypto: doc - Fix hash export state information
Date: Wed, 25 Jan 2017 17:18:05 +0100 [thread overview]
Message-ID: <5671933.EqcuFpxzUF@tauon.atsec.com> (raw)
In-Reply-To: <1485359706-7184-1-git-send-email-rabin.vincent@axis.com>
Am Mittwoch, 25. Januar 2017, 16:55:06 CET schrieb Rabin Vincent:
Hi Rabin,
> From: Rabin Vincent <rabinv@axis.com>
>
> The documentation states that crypto_ahash_reqsize() provides the size
> of the state structure used by crypto_ahash_export(). But it's actually
> crypto_ahash_statesize() which provides this size.
ack for the statesize documentation addition.
In addition, can you please add crypto_ahash_statesize to Documentation/
crypto/api-digest.rst.
nack - The documentation is quite right for reqsize: it returns the *request
data structure* size as documented.
Ciao
Stephan
next prev parent reply other threads:[~2017-01-25 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 15:55 [PATCH] crypto: doc - Fix hash export state information Rabin Vincent
2017-01-25 16:18 ` Stephan Müller [this message]
2017-01-26 15:33 ` Rabin Vincent
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=5671933.EqcuFpxzUF@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=rabin.vincent@axis.com \
--cc=rabinv@axis.com \
/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;
as well as URLs for NNTP newsgroup(s).