From: Shawn Guo <shawnguo@kernel.org>
To: Pankaj Gupta <pankaj.gupta@nxp.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Varun Sethi <V.Sethi@nxp.com>
Subject: Re: [PATCH v2] arm64: dts: imx8ulp-evk: add caam jr
Date: Tue, 18 Jul 2023 10:07:38 +0800 [thread overview]
Message-ID: <20230718020738.GX9559@dragon> (raw)
In-Reply-To: <DU2PR04MB86300C782DC7637C469599EC9526A@DU2PR04MB8630.eurprd04.prod.outlook.com>
On Mon, Jun 26, 2023 at 04:46:46AM +0000, Pankaj Gupta wrote:
> V2: Changed the email subject line.
> ------------------------------------------------
>
>
> Add crypto node in device tree for:
> - CAAM job-ring
>
> Signed-off-by: Varun Sethi <v.sethi@nxp.com>
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
The patch only changes imx8ulp SoC instead of imx8ulp-evk board,
so the patch subject should be:
arm64: dts: imx8ulp: ...
Shawn
next prev parent reply other threads:[~2023-07-18 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:40 [PATCH 1/9] arm64: dts: imx8ulp-evk: add caam jr Pankaj Gupta
2023-06-26 1:26 ` Peng Fan
2023-06-26 4:46 ` Pankaj Gupta
2023-06-26 4:46 ` [PATCH v2] " Pankaj Gupta
2023-07-10 5:27 ` Pankaj Gupta
2023-07-10 6:23 ` Krzysztof Kozlowski
2023-07-10 6:25 ` Krzysztof Kozlowski
2023-07-18 2:07 ` Shawn Guo [this message]
2023-07-18 4:50 ` [EXT] " Pankaj Gupta
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=20230718020738.GX9559@dragon \
--to=shawnguo@kernel.org \
--cc=V.Sethi@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).