[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <169164489346.20171.9690910658096738938.b4-ty@ti.com>
Date: Thu, 10 Aug 2023 00:22:20 -0500
From: Nishanth Menon <nm@...com>
To: <kristo@...nel.org>, <vigneshr@...com>, <d-gole@...com>,
<conor+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<afd@...com>, <robh+dt@...nel.org>
CC: Nishanth Menon <nm@...com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 00/13] Another round of K3 DTSI disables
Hi Andrew Davis,
On Wed, 9 Aug 2023 19:38:01 -0500, Andrew Davis wrote:
> Similar to a couple previous series on this, we disable by default
> nodes that cannot function standalone.
>
> This helps prevent folks from forgetting to disable unused nodes
> in their boards. One benefit of that is you can start out with
> an almost empty DTS file for a new board and have it still
> function without warnings or misbehaving hardware. Adding as you
> go, this helps ease bringup and upstreaming of new boards.
>
> [...]
Thank you for doing the cleanup.
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[01/13] arm64: dts: ti: k3-j721e: Enable SDHCI nodes at the board level
commit: 6fbd1310f99fc95d063b64d42addf701309663d6
[02/13] arm64: dts: ti: k3-j7200: Enable SDHCI nodes at the board level
commit: 013b7dd32c75ad3db218aa7a2d63f541304ac3b6
[03/13] arm64: dts: ti: k3-j721s2: Enable SDHCI nodes at the board level
commit: 5f715be31638b62de560acab7fdc7ff3d9e01bf9
[04/13] arm64: dts: ti: k3-am65: Enable OSPI nodes at the board level
commit: 46d0c519e44bf31f45dd0a62654c75cae76215b8
[05/13] arm64: dts: ti: k3-j721e: Enable OSPI nodes at the board level
commit: 73676c480b7286cb528170de73a7c03e19a5ade2
[06/13] arm64: dts: ti: k3-j7200: Enable OSPI nodes at the board level
commit: 1a576c89168422b0658f7831d6e1bad63252eaea
[07/13] arm64: dts: ti: k3-am64: Enable OSPI nodes at the board level
commit: cd9f6b324277d324ae056ffd8dda6287bcb649ab
[08/13] arm64: dts: ti: k3-j721e: Enable GPIO nodes at the board level
commit: 8757108b59e1490062d3c6a55ceccbafbee50e35
[09/13] arm64: dts: ti: k3-j721s2: Enable GPIO nodes at the board level
commit: 578bf4d09ef5d6e6707682ef0ae9d954ef77b8fb
[10/13] arm64: dts: ti: k3-j7200: Enable GPIO nodes at the board level
commit: d9fe476d39f62719adb805fc8c5668a3e21570d0
[11/13] arm64: dts: ti: k3-j721e: Enable TSCADC nodes at the board level
commit: a5a4cddad9ff71c55494328d0e39f051fe5905c2
[12/13] arm64: dts: ti: k3-am65: Enable TSCADC nodes at the board level
commit: 1228242df12ec1b7cd099c8e57a35940f32b89c3
[13/13] arm64: dts: ti: k3-am64: Enable TSCADC nodes at the board level
commit: bcd8a3f28ad6baec7f4d8cbb0fe7cbaf6e351567
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists