From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"Aymen Sghaier" <aymen.sghaier@nxp.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Will Deacon" <will@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
"Herbert Xu" <herbert@gondor.apana.org.au>
Subject: Re: [PATCH V3 3/3] arm64: defconfig: Enable CRYPTO_DEV_FSL_CAAM
Date: Mon, 23 Dec 2019 16:48:35 +0800 [thread overview]
Message-ID: <20191223084834.GW11523@dragon> (raw)
In-Reply-To: <20191218130616.13860-3-aford173@gmail.com>
On Wed, Dec 18, 2019 at 07:06:16AM -0600, Adam Ford wrote:
> Both the i.MX8MQ and i.MX8M Mini support the CAAM driver, but it
> is currently not enabled by default.
>
> This patch enables this as a module.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-23 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 13:06 [PATCH V3 1/3] crypto: caam: Add support for i.MX8M Mini Adam Ford
2019-12-18 13:06 ` [PATCH V3 2/3] arm64: dts: imx8mm: Add Crypto CAAM support Adam Ford
2019-12-23 8:48 ` Shawn Guo
2019-12-18 13:06 ` [PATCH V3 3/3] arm64: defconfig: Enable CRYPTO_DEV_FSL_CAAM Adam Ford
2019-12-20 7:08 ` Horia Geanta
2019-12-23 8:48 ` Shawn Guo [this message]
2019-12-27 10:38 ` [PATCH V3 1/3] crypto: caam: Add support for i.MX8M Mini 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=20191223084834.GW11523@dragon \
--to=shawnguo@kernel.org \
--cc=aford173@gmail.com \
--cc=aymen.sghaier@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).