From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Shenwei Wang <shenwei.wang@nxp.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<imx@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-imx@nxp.com>,
<openamp-rp@lists.openampproject.org>
Subject: Re: [PATCH v2 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver
Date: Thu, 2 Oct 2025 09:28:51 +0200 [thread overview]
Message-ID: <adc18aee-02bd-40e9-9b8b-10ceb2122460@foss.st.com> (raw)
In-Reply-To: <CACRpkdbB+DfhqUE-fsz_RQ1U02+nMEhNsXrKB4bd6dvLDLjWUQ@mail.gmail.com>
Hello Linus
On 10/1/25 08:57, Linus Walleij wrote:
> Hi Shenwei,
>
> thanks for your patch!
>
> This patch was not sent to the linux-gpio@vger.kernel.org
> mailing list, please include that or we can't merge the driver.
>
> I think the OpenAMP project should show interest in this
> patch series so I created an issue in their github:
> https://github.com/OpenAMP/website/issues/122
Thanks for pointing it out , i will do a review of this new version
Regards,
Arnaud
>
> After fixing the issues pointed out by Peng the driver
> looks good to me.
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2025-10-02 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 20:04 [PATCH v2 0/4] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2025-09-22 20:04 ` [PATCH v2 1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2025-10-01 20:47 ` Frank Li
2025-09-22 20:04 ` [PATCH v2 2/4] remoteproc: imx_rproc: Populate devices under "rpmsg" subnode Shenwei Wang
2025-09-28 8:47 ` Peng Fan
2025-10-01 20:09 ` Shenwei Wang
2025-09-22 20:04 ` [PATCH v2 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver Shenwei Wang
2025-09-24 17:07 ` kernel test robot
2025-09-29 3:37 ` Peng Fan
2025-09-29 14:59 ` Shenwei Wang
2025-10-01 6:57 ` Linus Walleij
2025-10-02 7:28 ` Arnaud POULIQUEN [this message]
2025-10-03 7:40 ` Arnaud POULIQUEN
2025-10-03 18:41 ` Shenwei Wang
2025-10-06 9:52 ` Arnaud POULIQUEN
2025-10-06 14:33 ` Shenwei Wang
2025-10-07 9:16 ` Arnaud POULIQUEN
2025-09-22 20:04 ` [PATCH v2 4/4] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc Shenwei Wang
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=adc18aee-02bd-40e9-9b8b-10ceb2122460@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@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=mathieu.poirier@linaro.org \
--cc=openamp-rp@lists.openampproject.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@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).