From: Iuliana Prodan <iuliana.prodan@nxp.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>,
"S.J. Wang" <shengjiu.wang@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Bjorn Andersson <andersson@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-imx <linux-imx@nxp.com>,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
LnxRevLi <LnxRevLi@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Mpuaudiosw <Mpuaudiosw@nxp.com>,
"Iuliana Prodan (OSS)" <iuliana.prodan@oss.nxp.com>
Subject: Re: [PATCH 2/2] arm64: dts: imx8mp: add reserve-memory nodes for DSP
Date: Tue, 12 Sep 2023 13:51:42 +0300 [thread overview]
Message-ID: <dc402d33-88b1-e828-e6a5-2de060fbcdca@nxp.com> (raw)
In-Reply-To: <af1959ce-d817-2a9e-9c28-fed8c608a3df@linaro.org>
On 9/12/2023 12:36 PM, Krzysztof Kozlowski wrote:
> On 12/09/2023 10:49, Iuliana Prodan wrote:
>>>> Should I test this on other tree(s)?
>>> You test the patch on the tree you send it. What is the point to test it
>>> on some old code, cherry-pick with bugs and then send?
>>>
>>> If you have cross-tree dependencies between subsystem, isn't linux-next
>>> for this?
>> TBH, I don't know, that's why I asked.
>>
>> For sure one patch is for remoteproc.
>> For the other, I don't know who will pick it, but I'll tested on
>> linux-next, as you suggested.
> MAINTAINERS file (and get_maintainers.pl) will tell you. Specifically,
> this does not look really related to remoteproc patch, so it should not
> be together in one patchset.
Hi Mathieu,
I need to send a v2 - to fix the dtsi missing bracket on patch 2.
So, should I keep the 2 patches together or send them separately?
Thanks,
Iulia
next prev parent reply other threads:[~2023-09-12 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 22:44 [PATCH 0/2] Rpmsg support for i.MX DSP with resource table Iuliana Prodan (OSS)
2023-09-11 22:44 ` [PATCH 1/2] remoteproc: imx_dsp_rproc: add mandatory find_loaded_rsc_table op Iuliana Prodan (OSS)
2023-09-11 22:44 ` [PATCH 2/2] arm64: dts: imx8mp: add reserve-memory nodes for DSP Iuliana Prodan (OSS)
2023-09-12 7:07 ` Krzysztof Kozlowski
2023-09-12 8:13 ` Iuliana Prodan
2023-09-12 8:26 ` Krzysztof Kozlowski
2023-09-12 8:49 ` Iuliana Prodan
2023-09-12 9:36 ` Krzysztof Kozlowski
2023-09-12 10:51 ` Iuliana Prodan [this message]
2023-09-12 14:41 ` Mathieu Poirier
2023-09-12 10:58 ` Daniel Baluta
2023-09-12 11:30 ` Marco Felsch
2023-09-12 11:33 ` Iuliana Prodan
2023-09-12 11:42 ` Marco Felsch
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=dc402d33-88b1-e828-e6a5-2de060fbcdca@nxp.com \
--to=iuliana.prodan@nxp.com \
--cc=LnxRevLi@nxp.com \
--cc=Mpuaudiosw@nxp.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=iuliana.prodan@oss.nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.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).