From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: bjorn.andersson@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V2 0/2] remoteproc: add i.MX93 support
Date: Mon, 9 May 2022 09:46:17 -0600 [thread overview]
Message-ID: <20220509154617.GA2969947@p14s> (raw)
In-Reply-To: <20220429005346.2108279-1-peng.fan@oss.nxp.com>
On Fri, Apr 29, 2022 at 08:53:44AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> V2:
> CC dt maintainers
> Reorder compatible strings in alphabetical order in patch 1
>
> i.MX93 features a general purpose M33 core, support in with this patchset.
>
> Peng Fan (2):
> dt-bindings: remoteproc: imx_rproc: support i.MX93
> remoteproc: imx_rproc: support i.MX93
>
> .../bindings/remoteproc/fsl,imx-rproc.yaml | 9 ++---
> drivers/remoteproc/imx_rproc.c | 33 +++++++++++++++++++
> 2 files changed, 38 insertions(+), 4 deletions(-)
I have applied this set.
Thanks,
Mathieu
>
> --
> 2.25.1
>
prev parent reply other threads:[~2022-05-09 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 0:53 [PATCH V2 0/2] remoteproc: add i.MX93 support Peng Fan (OSS)
2022-04-29 0:53 ` [PATCH V2 1/2] dt-bindings: remoteproc: imx_rproc: support i.MX93 Peng Fan (OSS)
2022-04-29 21:01 ` Krzysztof Kozlowski
2022-04-29 0:53 ` [PATCH V2 2/2] " Peng Fan (OSS)
2022-05-09 15:46 ` Mathieu Poirier [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=20220509154617.GA2969947@p14s \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.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=linux-remoteproc@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).