[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <171984950183.3152309.11635024979528305029.b4-ty@ti.com>
Date: Wed, 3 Jul 2024 10:02:01 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
Rob Herring
<robh+dt@...nel.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Jan
Kiszka <jan.kiszka@...mens.com>, Andrew Davis <afd@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] Add MAC eFuse nodes to sys config areas
Hi Andrew Davis,
On Fri, 28 Jun 2024 10:15:11 -0500, Andrew Davis wrote:
> Patches are all mostly the same but split by platform, context is in
> the patches.
>
> End result is fewer DTB check warnings, some platforms now have 0 :)
>
> This series is a replacement for this patch[0].
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/7] arm64: dts: ti: k3-am65: Add cpsw-mac-efuse node to mcu_conf
commit: 0ab18cecc806586144ea8f245d15a8da71c332eb
[2/7] arm64: dts: ti: k3-j7200: Add cpsw-mac-efuse node to mcu_conf
commit: 3128edb3c4a8ad8f7c53d11fc5a21da5d6b597ba
[3/7] arm64: dts: ti: k3-j721e: Add cpsw-mac-efuse node to mcu_conf
commit: 1147fa465a82db96f9883477c3351b77a48e457c
[4/7] arm64: dts: ti: k3-j721s2: Add cpsw-mac-efuse node to mcu_conf
commit: 418291e705a9824b09f76858c374b04cf4e7a1d3
[5/7] arm64: dts: ti: k3-j784s4: Add cpsw-mac-efuse node to mcu_conf
commit: 74e074d22a4161c86b3acc12d6fc1dbd60b177f9
[6/7] arm64: dts: ti: k3-am62a: Add cpsw-mac-efuse node to wkup_conf
commit: 00d20114b515b4697af228cf3c01120ca1335270
[7/7] arm64: dts: ti: k3-am62: Add cpsw-mac-efuse node to wkup_conf
commit: c870321e4317ea28443e12445f070b35089fd45e
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
--
Vignesh
Powered by blists - more mailing lists