Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@google.com>
Cc: linux-crypto@vger.kernel.org, "David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH 0/4] crypto: gf128mul cleanups
Date: Thu, 9 Mar 2017 18:46:09 +0800	[thread overview]
Message-ID: <20170309104609.GA7185@gondor.apana.org.au> (raw)
In-Reply-To: <20170214214330.99845-1-ebiggers@google.com>

On Tue, Feb 14, 2017 at 01:43:26PM -0800, Eric Biggers wrote:
> This patchset makes a few cleanups to the generic GF(2^128) multiplication code
> to make it slightly easier to understand and modify.  No functional changes are
> intended.
> 
> Eric Biggers (4):
>   crypto: gf128mul - fix some comments
>   crypto: gf128mul - remove xx() macro
>   crypto: gf128mul - rename the byte overflow tables
>   crypto: gf128mul - constify 4k and 64k multiplication tables
> 
>  crypto/gf128mul.c         | 86 +++++++++++++++++++++++++++--------------------
>  include/crypto/gf128mul.h | 32 +++++++++---------
>  2 files changed, 67 insertions(+), 51 deletions(-)

All 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

      parent reply	other threads:[~2017-03-09 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 21:43 [PATCH 0/4] crypto: gf128mul cleanups Eric Biggers
2017-02-14 21:43 ` [PATCH 1/4] crypto: gf128mul - fix some comments Eric Biggers
2017-02-14 21:43 ` [PATCH 2/4] crypto: gf128mul - remove xx() macro Eric Biggers
2017-02-14 21:43 ` [PATCH 3/4] crypto: gf128mul - rename the byte overflow tables Eric Biggers
2017-02-14 21:43 ` [PATCH 4/4] crypto: gf128mul - constify 4k and 64k multiplication tables Eric Biggers
2017-03-09 10:46 ` 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=20170309104609.GA7185@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=linux-crypto@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