From: Nishanth Menon <nm@ti.com>
To: Hari Nagalla <hnagalla@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Add R5F and C71 DSP nodes for J784S4 SoC
Date: Fri, 31 Mar 2023 10:51:06 -0500 [thread overview]
Message-ID: <20230331155106.fqz34ocerrgd6vnw@facility> (raw)
In-Reply-To: <28d0ce4d-afca-55ee-b471-fe02e71ab262@ti.com>
On 04:31-20230331, Hari Nagalla wrote:
> On 3/30/23 09:55, Nishanth Menon wrote:
> > > arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 168 ++++++++++++++++++
> > > .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 40 +++++
> > > 2 files changed, 208 insertions(+)
> > >
> > > --
> > > 2.17.1
> > >
> > No specific need for board file memory reservations for DDR?
> They are needed in board file, but to be submitted in separate patch set.
Sorry, NAK, please submit as a single series.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-31 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:15 [PATCH v2 0/2] Add R5F and C71 DSP nodes for J784S4 SoC Hari Nagalla
2023-03-30 14:15 ` [PATCH v2 1/2] arm64: dts: ti: k3-j784s4-main: Add R5F cluster nodes Hari Nagalla
2023-03-30 14:15 ` [PATCH v2 2/2] arm64: dts: ti: k3-j784s4-main: Add C71x DSP nodes Hari Nagalla
2023-03-30 14:55 ` [PATCH v2 0/2] Add R5F and C71 DSP nodes for J784S4 SoC Nishanth Menon
2023-03-31 9:31 ` Hari Nagalla
2023-03-31 15:51 ` Nishanth Menon [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=20230331155106.fqz34ocerrgd6vnw@facility \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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