linux-kernel - Re: [PATCH v3 0/4] Add overlays to disable optional hardware in k3-am6xx-phycore-som boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 21 Jun 2024 20:53:35 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, Nathan Morrisson <nmorrisson@...tec.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <upstream@...ts.phytec.de>,
        <w.egorov@...tec.de>
Subject: Re: [PATCH v3 0/4] Add overlays to disable optional hardware in k3-am6xx-phycore-som boards

Hi Nathan Morrisson,

On Thu, 13 Jun 2024 16:07:55 -0700, Nathan Morrisson wrote:
> Add three overlays to disable the eth phy, rtc, and spi nor. These
> overlays will be used to disable device tree nodes for components
> that are optionally not populated.
> 
> v3:
>   - Explain the logic behind adding the overlays in commit messages
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/4] arm64: dts: ti: k3-am64-phycore-som: Add serial_flash label
      commit: 1fc3858a906bf3e8c48a14587106bb61c2f8d7c5
[2/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable eth phy
      commit: 1322b1796d7143dfa75e10e036c6099927ef510d
[3/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable rtc
      commit: a0b552605f8c588fdd9ea062886fb90d50534a8d
[4/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable spi nor
      commit: 9a32378884931d8f66d0d7122873156199fa422f

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