From: "Maxime Ripard" <mripard@kernel.org>
To: "Nishanth Menon" <nm@ti.com>
Cc: u-boot@lists.denx.de, "Andrew Davis" <afd@ti.com>,
"Bryan Brattlof" <bb@ti.com>,
"Francesco Dolcini" <francesco@dolcini.it>,
"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
"Mattijs Korpershoek" <mkorpershoek@baylibre.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Neha Malcom Francis" <n-francis@ti.com>,
"Nikhil Jain" <n-jain1@ti.com>,
"Roger Quadros" <rogerq@kernel.org>,
"Sjoerd Simons" <sjoerd@collabora.com>,
"Tom Rini" <trini@konsulko.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Wadim Egorov" <w.egorov@phytec.de>
Subject: Re: [PATCH V3 3/3] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1
Date: Fri, 28 Jul 2023 12:45:14 +0000 [thread overview]
Message-ID: <41d9c2517e6333c8462322a80da2f2ea.mripard@kernel.org> (raw)
In-Reply-To: <20230727090331.2834463-4-nm@ti.com>
On Thu, 27 Jul 2023 04:03:31 -0500, Nishanth Menon wrote:
> Update the am62 and am625 device-trees from linux v6.5-rc1. This needed
> the following tweaks to the u-boot specific dtsi as well:
> - Switch tick-timer to the main_timer as it's now defined in the main dtsi
> - Secure proxies are defined in SoC dtsi
> - Drop duplicate nodes - u-boot.dtsi is includes in r5-sk, no need for
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2023-07-28 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 9:03 [PATCH V3 0/3] arm: dts: Sync k3-am62 with upstream kernel Nishanth Menon
2023-07-27 9:03 ` [PATCH V3 1/3] omap: timer: add ti,am654-timer compatibility Nishanth Menon
2023-07-28 16:50 ` Tom Rini
2023-07-27 9:03 ` [PATCH V3 2/3] arm: mach-k3: am62: Add timer0 id to the dev list Nishanth Menon
2023-07-28 16:50 ` Tom Rini
2023-07-27 9:03 ` [PATCH V3 3/3] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1 Nishanth Menon
2023-07-28 12:45 ` Maxime Ripard [this message]
2023-07-28 16:51 ` Tom Rini
2023-07-28 12:45 ` [PATCH V3 0/3] arm: dts: Sync k3-am62 with upstream kernel Maxime Ripard
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=41d9c2517e6333c8462322a80da2f2ea.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=marcel.ziswiler@toradex.com \
--cc=mkorpershoek@baylibre.com \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=sjoerd@collabora.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.