From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: [PATCH 0/2] crc-t10dif library improvements
Date: Tue, 9 Jun 2020 23:39:41 -0700 [thread overview]
Message-ID: <20200610063943.378796-1-ebiggers@kernel.org> (raw)
This series makes some more improvements to lib/crc-t10dif.c, as discussed at
https://lkml.kernel.org/linux-crypto/20200604063324.GA28813@gondor.apana.org.au/T/#u
This applies on top of Herbert's
"[v2 PATCH] crc-t10dif: Fix potential crypto notify dead-lock".
Eric Biggers (2):
crc-t10dif: use fallback in initial state
crc-t10dif: clean up some more things
lib/crc-t10dif.c | 61 +++++++++++++++++-------------------------------
1 file changed, 21 insertions(+), 40 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-10 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 6:39 Eric Biggers [this message]
2020-06-10 6:39 ` [PATCH 1/2] crc-t10dif: use fallback in initial state Eric Biggers
2020-06-10 6:39 ` [PATCH 2/2] crc-t10dif: clean up some more things Eric Biggers
2020-06-18 7:58 ` [PATCH 0/2] crc-t10dif library improvements Herbert Xu
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=20200610063943.378796-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=martin.petersen@oracle.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).