mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, Andrew Davis <afd@ti.com>,
	Nishanth Menon <nm@ti.com>
Subject: [PATCH V3 0/3] arm64: dts: ti: k3-am65: dtbs_check warnings fixups
Date: Wed, 7 Jun 2023 08:20:40 -0500	[thread overview]
Message-ID: <20230607132043.3932726-1-nm@ti.com> (raw)

Hi,

Hopefully, third time is a charm ;)

Series of minor fixups for AM65x device tree to cleanup some of the
dtbs_check warnings.


Changes Since V2:
* Dropped mux-controller fixup (should have been dropped when
  dependencies changed)

V2: https://lore.kernel.org/all/20230606160643.3618390-1-nm@ti.com/
V1: https://lore.kernel.org/all/20230424144949.244135-1-nm@ti.com/


Nishanth Menon (3):
  arm64: dts: ti: k3-am65-main: Fix mcan node name
  arm64: dts: ti: k3-am65-main: Drop deprecated ti,otap-del-sel property
  arm64: dts: ti: k3-am65-iot2050-common: Rename rtc8564 nodename

 arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 2 +-
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi           | 1 -
 arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi            | 4 ++--
 3 files changed, 3 insertions(+), 4 deletions(-)

-- 
2.40.0


             reply	other threads:[~2023-06-07 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 13:20 Nishanth Menon [this message]
2023-06-07 13:20 ` [PATCH V3 1/3] arm64: dts: ti: k3-am65-main: Fix mcan node name Nishanth Menon
2023-06-07 13:20 ` [PATCH V3 2/3] arm64: dts: ti: k3-am65-main: Drop deprecated ti,otap-del-sel property Nishanth Menon
2023-06-07 13:20 ` [PATCH V3 3/3] arm64: dts: ti: k3-am65-iot2050-common: Rename rtc8564 nodename Nishanth Menon
2023-06-15 13:13 ` [PATCH V3 0/3] arm64: dts: ti: k3-am65: dtbs_check warnings fixups Vignesh Raghavendra

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=20230607132043.3932726-1-nm@ti.com \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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 \
    /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®