From: Shawn Guo <shawnguo@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] ARM: dts: imx: use generic name for crypto node
Date: Wed, 11 Mar 2020 16:53:58 +0800 [thread overview]
Message-ID: <20200311085357.GG29269@dragon> (raw)
In-Reply-To: <20200305135909.8180-1-horia.geanta@nxp.com>
On Thu, Mar 05, 2020 at 03:59:04PM +0200, Horia Geantă wrote:
> This patch set aligns / fixes the naming of the crypto node
> (and its child nodes) for sahara, dcp and caam crypto engines
> used in i.MX SoCs.
>
> Horia Geantă (4):
> dt-bindings: crypto: sahara: use generic node name
> dt-bindings: crypto: dcp: use generic node name
> dt-bindings: crypto: caam: use generic node name
> ARM: dts: imx: align name for crypto node and child nodes
>
> Silvano di Ninno (1):
> arm64: dts: imx8mn: align name for crypto child nodes
Applied all, thanks.
prev parent reply other threads:[~2020-03-11 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 13:59 [PATCH 0/5] ARM: dts: imx: use generic name for crypto node Horia Geantă
2020-03-05 13:59 ` [PATCH 1/5] dt-bindings: crypto: sahara: use generic node name Horia Geantă
2020-03-05 13:59 ` [PATCH 2/5] dt-bindings: crypto: dcp: " Horia Geantă
2020-03-05 13:59 ` [PATCH 3/5] dt-bindings: crypto: caam: " Horia Geantă
2020-03-05 13:59 ` [PATCH 4/5] ARM: dts: imx: align name for crypto node and child nodes Horia Geantă
2020-03-05 13:59 ` [PATCH 5/5] arm64: dts: imx8mn: align name for crypto " Horia Geantă
2020-03-11 8:53 ` Shawn Guo [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=20200311085357.GG29269@dragon \
--to=shawnguo@kernel.org \
--cc=aymen.sghaier@nxp.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=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=silvano.dininno@nxp.com \
/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).