From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: tim.c.chen@linux.intel.com,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: Tree for May 15 (crypto /crct10dif)
Date: Thu, 16 May 2013 09:22:30 +0200 [thread overview]
Message-ID: <CAMuHMdUmD2DMNeezetHNbe9DgQXpTN4BEfEmJSztyzCivQpyXQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305161152530.31865@M2420>
On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou <jencce.kernel@gmail.com> wrote:
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
>
> config CRYPTO_CRCT10DIF
> tristate "CRCT10DIF algorithm"
> + depends on CRC_T10DIF
This is a library symbol, so "select CRC_T10DIF"?
> select CRYPTO_HASH
> help
> CRC T10 Data Integrity Field computation is being cast as
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-05-16 7:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 3:26 linux-next: Tree for May 15 Stephen Rothwell
2013-05-15 17:42 ` linux-next: Tree for May 15 (wireless/brcm) Randy Dunlap
2013-05-15 17:59 ` linux-next: Tree for May 15 (crypto /crct10dif) Randy Dunlap
2013-05-16 3:57 ` Xiong Zhou
2013-05-16 7:22 ` Geert Uytterhoeven [this message]
2013-05-16 16:09 ` Tim Chen
2013-05-16 16:59 ` Tim Chen
2013-05-16 18:03 ` Tim Chen
2013-05-17 3:09 ` Xiong Zhou
2013-05-20 11:47 ` Herbert Xu
2013-05-20 12:14 ` Herbert Xu
2013-05-20 19:09 ` Tim Chen
2013-05-21 13:46 ` Herbert Xu
2013-05-17 3:06 ` Xiong Zhou
2013-05-15 21:03 ` [PATCH -next] platform/x86: fix amilo-rfkill build errors Randy Dunlap
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=CAMuHMdUmD2DMNeezetHNbe9DgQXpTN4BEfEmJSztyzCivQpyXQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=jencce.kernel@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tim.c.chen@linux.intel.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