From: Herbert Xu <herbert@gondor.apana.org.au>
To: David Yang <mmyangfl@gmail.com>
Cc: linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] crypto: engine - Fix struct crypto_engine_op doc
Date: Fri, 12 May 2023 18:59:13 +0800 [thread overview]
Message-ID: <ZF4cAXSN3xHqlwWg@gondor.apana.org.au> (raw)
In-Reply-To: <20230424172021.2893856-1-mmyangfl@gmail.com>
On Tue, Apr 25, 2023 at 01:20:21AM +0800, David Yang wrote:
> Remove redundant underscore and fix some grammar in prepare_request doc.
>
> Signed-off-by: David Yang <mmyangfl@gmail.com>
> ---
> v2: fix description too
> v3: remove inappropriate commit tags
> include/crypto/engine.h | 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
prev parent reply other threads:[~2023-05-12 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 17:20 [PATCH v3] crypto: engine - Fix struct crypto_engine_op doc David Yang
2023-04-24 19:05 ` Randy Dunlap
2023-05-12 10:59 ` 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=ZF4cAXSN3xHqlwWg@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=mmyangfl@gmail.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