From: Herbert Xu <herbert@gondor•apana.org.au>
To: Seth Jennings <sjenning@linux•vnet.ibm.com>
Cc: Michael Neuling <mikey@neuling•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Kent Yoder <key@linux•vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
anton@samba•org
Subject: Re: [PATCH v2] powerpc/crypto: fix defconfig break
Date: Wed, 1 Aug 2012 17:49:31 +0800 [thread overview]
Message-ID: <20120801094931.GA15975@gondor.apana.org.au> (raw)
In-Reply-To: <1343794529-28329-1-git-send-email-sjenning@linux.vnet.ibm.com>
On Tue, Jul 31, 2012 at 11:15:29PM -0500, Seth Jennings wrote:
> As part of the Kconfig rework for drivers/crypto/nx, the meaning of
> CONFIG_CRYPTO_DEV_NX was changed. At the same time this commit was
> heading upstream
>
> fd297b3a7302ab866306f53c1fd1e97b083fe83e
> powerpc: Enable pseries hardware RNG and crypto module
>
> still used the old meaning, set CONFIG_CRYPTO_DEV_NX=m when it
> is now a bool in the Kconfig. This patch repairs the break.
>
> Reported-by: Michael Neuling <mikey@neuling•org>
> Signed-off-by: Seth Jennings <sjenning@linux•vnet.ibm.com>
> ---
> This patch is based on Linus master which already contains
> the commit above. Please apply this patch before my patchset
> (powerpc/crypto: IBM Power7+ in-Nest compression support) to
> avoid the defconfig break.
OK, I've rebased my tree and folded this into
commit 322cacce0a3c36d3ad89d8836b9ed6fcb06e1a61
Author: Seth Jennings <sjenning@linux•vnet.ibm.com>
Date: Thu Jul 19 09:42:38 2012 -0500
powerpc/crypto: rework Kconfig
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
prev parent reply other threads:[~2012-08-01 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 4:15 [PATCH v2] powerpc/crypto: fix defconfig break Seth Jennings
2012-08-01 4:36 ` Michael Neuling
2012-08-01 9:49 ` 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=20120801094931.GA15975@gondor.apana.org.au \
--to=herbert@gondor$(echo .)apana.org.au \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=key@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mikey@neuling$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sjenning@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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