From: Marek Vasut <marex@denx.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] crypto: mxs-dcp is an stmp device
Date: Mon, 12 Oct 2015 16:00:55 +0200 [thread overview]
Message-ID: <201510121600.55665.marex@denx.de> (raw)
In-Reply-To: <6543300.PJNp8A08gY@wuerfel>
On Monday, October 12, 2015 at 03:52:34 PM, Arnd Bergmann wrote:
> The mxs-dcp driver relies on the stmp_reset_block() helper function, which
> is provided by CONFIG_STMP_DEVICE. This symbol is always set on MXS,
> but the driver can now also be built for MXC (i.MX6)
That is correct.
> , which results in a built error if no other driver selects STMP_DEVICE:
Ouch.
> drivers/built-in.o: In function `mxs_dcp_probe':
> vf610-ocotp.c:(.text+0x3df302): undefined reference to `stmp_reset_block'
>
> This adds the 'select', like all other stmp drivers have it.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: a2712e6c75f ("crypto: mxs-dcp - Allow MXS_DCP to be used on MX6SL")
Acked-by: Marek Vasut <marex@denx.de>
> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> index ab7e3b668890..2569e043317e 100644
> --- a/drivers/crypto/Kconfig
> +++ b/drivers/crypto/Kconfig
> @@ -430,6 +430,7 @@ endif
> config CRYPTO_DEV_MXS_DCP
> tristate "Support for Freescale MXS DCP"
> depends on (ARCH_MXS || ARCH_MXC)
> + select STMP_DEVICE
> select CRYPTO_CBC
> select CRYPTO_ECB
> select CRYPTO_AES
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-10-12 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 13:52 [PATCH] crypto: mxs-dcp is an stmp device Arnd Bergmann
2015-10-12 14:00 ` Marek Vasut [this message]
2015-10-14 14:28 ` 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=201510121600.55665.marex@denx.de \
--to=marex@denx.de \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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