From: Ondrej Mosnacek <omosnacek@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ondrej Mosnacek <omosnacek@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
Milan Broz <gmazyland@gmail.com>
Subject: [PATCH v5 4/4] crypto: xts - drop gf128mul dependency
Date: Sun, 2 Apr 2017 21:19:16 +0200 [thread overview]
Message-ID: <20170402191916.9309-5-omosnacek@gmail.com> (raw)
In-Reply-To: <20170402191916.9309-1-omosnacek@gmail.com>
Since the gf128mul_x_ble function used by xts.c is now defined inline
in the header file, the XTS module no longer depends on gf128mul.
Therefore, the 'select CRYPTO_GF128MUL' line can be safely removed.
Signed-off-by: Ondrej Mosnacek <omosnacek@gmail.com>
---
crypto/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 6854c1f..aac4bc9 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -374,7 +374,6 @@ config CRYPTO_XTS
tristate "XTS support"
select CRYPTO_BLKCIPHER
select CRYPTO_MANAGER
- select CRYPTO_GF128MUL
select CRYPTO_ECB
help
XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
--
2.9.3
next prev parent reply other threads:[~2017-04-02 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 19:19 [PATCH v5 0/4] gf128mul refactoring Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 1/4] crypto: gf128mul - define gf128mul_x_* in gf128mul.h Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 2/4] crypto: gf128mul - switch gf128mul_x_ble to le128 Ondrej Mosnacek
2017-04-02 19:19 ` [PATCH v5 3/4] crypto: glue_helper - remove the le128_gf128mul_x_ble function Ondrej Mosnacek
2017-04-02 19:19 ` Ondrej Mosnacek [this message]
2017-04-05 4:13 ` [PATCH v5 0/4] gf128mul refactoring Eric Biggers
2017-04-05 14:11 ` 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=20170402191916.9309-5-omosnacek@gmail.com \
--to=omosnacek@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--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