From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: configs: Switching to the new Marvell's cryptographic engine driver for mvebu_v5_defconfig
Date: Wed, 30 Mar 2016 11:54:22 +0200 [thread overview]
Message-ID: <87egasuw8h.fsf@free-electrons.com> (raw)
In-Reply-To: <1459238548-28029-1-git-send-email-romain.perier@free-electrons.com> (Romain Perier's message of "Tue, 29 Mar 2016 10:02:28 +0200")
Hi Romain,
On mar., mars 29 2016, Romain Perier <romain.perier@free-electrons.com> wrote:
> This enables the new driver for Marvell CESA crypto engines on all mvebu v5.
> The old driver is no longer used, but it is still in the tree for fallback.
>
> Signed-off-by: Romain Perier <romain.perier@free-electrons.com>
As we already spoke about it with Andrew and Jason I applied it on
mvebu/defconfig.
Thanks,
Gregory
> ---
> arch/arm/configs/mvebu_v5_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/configs/mvebu_v5_defconfig b/arch/arm/configs/mvebu_v5_defconfig
> index 4562006..6051c51 100644
> --- a/arch/arm/configs/mvebu_v5_defconfig
> +++ b/arch/arm/configs/mvebu_v5_defconfig
> @@ -208,8 +208,8 @@ CONFIG_DEBUG_KERNEL=y
> # CONFIG_DEBUG_PREEMPT is not set
> # CONFIG_FTRACE is not set
> CONFIG_DEBUG_USER=y
> +CONFIG_CRYPTO_DEV_MARVELL_CESA=y
> CONFIG_CRYPTO_CBC=m
> CONFIG_CRYPTO_PCBC=m
> -CONFIG_CRYPTO_DEV_MV_CESA=y
> CONFIG_CRC_CCITT=y
> CONFIG_LIBCRC32C=y
> --
> 2.7.4
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2016-03-30 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 8:02 [PATCH] ARM: configs: Switching to the new Marvell's cryptographic engine driver for mvebu_v5_defconfig Romain Perier
2016-03-30 9:54 ` Gregory CLEMENT [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=87egasuw8h.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.