From: Nishanth Menon <nm@ti.com>
To: Tero Kristo <kristo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/4] arm64: dts: ti: k3-*: Fixup nodes to exposed to be non-compliant with yaml
Date: Mon, 10 May 2021 09:50:29 -0500 [thread overview]
Message-ID: <20210510145033.7426-1-nm@ti.com> (raw)
Hi,
Series of minor fixups for v5.13-rc1 for compliance exposed by yaml
conversion in the series:
https://lore.kernel.org/linux-arm-kernel/20210503190824.GA2192378@robh.at.kernel.org/#t
Minimal testing performed on k3 platforms.
If possible, will be good to get in 5.13 window.
Nishanth Menon (4):
arm64: dts: ti: k3-*: Rename the TI-SCI clocks node name
arm64: dts: ti: k3-am65-wakeup: Add debug region to TI-SCI node
arm64: dts: ti: k3-am65-wakeup: Drop un-necessary properties from dmsc
node
arm64: dts: ti: k3-*: Rename the TI-SCI node
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 10 +++++-----
arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++--
4 files changed, 11 insertions(+), 11 deletions(-)
--
2.31.0
next reply other threads:[~2021-05-10 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:50 Nishanth Menon [this message]
2021-05-10 14:50 ` [PATCH 1/4] arm64: dts: ti: k3-*: Rename the TI-SCI clocks node name Nishanth Menon
2021-05-10 14:50 ` [PATCH 2/4] arm64: dts: ti: k3-am65-wakeup: Add debug region to TI-SCI node Nishanth Menon
2021-05-10 14:50 ` [PATCH 3/4] arm64: dts: ti: k3-am65-wakeup: Drop un-necessary properties from dmsc node Nishanth Menon
2021-05-10 14:50 ` [PATCH 4/4] arm64: dts: ti: k3-*: Rename the TI-SCI node Nishanth Menon
2021-05-11 7:17 ` [PATCH 0/4] arm64: dts: ti: k3-*: Fixup nodes to exposed to be non-compliant with yaml Tero Kristo
2021-05-14 17:52 ` Nishanth Menon
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=20210510145033.7426-1-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®