From: Herbert Xu <herbert@gondor.apana.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/6] crypto: delete or fix duplicated words
Date: Fri, 21 Aug 2020 17:55:30 +1000 [thread overview]
Message-ID: <20200821075529.GC25143@gondor.apana.org.au> (raw)
In-Reply-To: <20200731023924.8829-1-rdunlap@infradead.org>
On Thu, Jul 30, 2020 at 07:39:18PM -0700, Randy Dunlap wrote:
> Drop doubled words or fix them to what they should be.
>
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: linux-crypto@vger.kernel.org
>
> crypto/algif_aead.c | 2 +-
> crypto/asymmetric_keys/pkcs7_parser.h | 2 +-
> crypto/crc32c_generic.c | 4 ++--
> crypto/crct10dif_generic.c | 2 +-
> crypto/crypto_engine.c | 2 +-
> crypto/tcrypt.c | 4 ++--
> 6 files changed, 8 insertions(+), 8 deletions(-)
Patches 1,3-6 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:[~2020-08-21 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 2:39 [PATCH 0/6] crypto: delete or fix duplicated words Randy Dunlap
2020-07-31 2:39 ` [PATCH 1/6] crypto: algif_aead: delete duplicated word Randy Dunlap
2020-07-31 2:39 ` [PATCH 2/6] crypto: asymmetric_keys: pkcs7_parser: " Randy Dunlap
2020-07-31 2:39 ` [PATCH 3/6] crypto: crc32c_generic: delete and fix duplicated words Randy Dunlap
2020-07-31 2:39 ` [PATCH 4/6] crypto: crct10dif_generic: " Randy Dunlap
2020-07-31 2:39 ` [PATCH 5/6] crypto: crypto_engine: delete duplicated word Randy Dunlap
2020-07-31 2:39 ` [PATCH 6/6] crypto: tcrypt: delete duplicated words in messages Randy Dunlap
2020-08-21 7:55 ` 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=20200821075529.GC25143@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=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).