LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	Paul Mackerras <paulus@samba.org>,
	Andreas Westin <andreas.westin@stericsson.com>,
	Kent Yoder <key@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: linux-next: manual merge of the crypto tree with the powerpc tree
Date: Thu, 17 May 2012 13:21:16 +1000	[thread overview]
Message-ID: <20120517132116.8a5378bce254fc39d20cb08a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

Hi Herbert,

Today's linux-next merge of the crypto tree got a conflict in
drivers/crypto/Kconfig between commit aef7b31c8833 ("powerpc/crypto:
Build files for the nx device driver") from the powerpc tree and commit
2789c08fffea ("crypto: ux500 - Add driver for CRYP hardware") from the
crypto tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/crypto/Kconfig
index f1ceeef,69fdf18..0000000
--- a/drivers/crypto/Kconfig
+++ b/drivers/crypto/Kconfig
@@@ -296,21 -295,15 +296,32 @@@ config CRYPTO_DEV_TEGRA_AE
  	  To compile this driver as a module, choose M here: the module
  	  will be called tegra-aes.
  
 +config CRYPTO_DEV_NX
 +	tristate "Support for Power7+ in-Nest cryptographic accleration"
 +	depends on PPC64 && IBMVIO
 +	select CRYPTO_AES
 +	select CRYPTO_CBC
 +	select CRYPTO_ECB
 +	select CRYPTO_CCM
 +	select CRYPTO_GCM
 +	select CRYPTO_AUTHENC
 +	select CRYPTO_XCBC
 +	select CRYPTO_SHA256
 +	select CRYPTO_SHA512
 +	help
 +	  Support for Power7+ in-Nest cryptographic acceleration. This
 +	  module supports acceleration for AES and SHA2 algorithms. If you
 +	  choose 'M' here, this module will be called nx_crypto.
 +
+ config CRYPTO_DEV_UX500
+ 	tristate "Driver for ST-Ericsson UX500 crypto hardware acceleration"
+ 	depends on ARCH_U8500
+ 	select CRYPTO_ALGAPI
+ 	help
+ 	  Driver for ST-Ericsson UX500 crypto engine.
+ 
+ if CRYPTO_DEV_UX500
+ 	source "drivers/crypto/ux500/Kconfig"
+ endif # if CRYPTO_DEV_UX500
+ 
  endif # CRYPTO_HW

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-05-17  3:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  3:21 Stephen Rothwell [this message]
2012-05-17  3:22 ` linux-next: manual merge of the crypto tree with the powerpc tree 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=20120517132116.8a5378bce254fc39d20cb08a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andreas.westin@stericsson.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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