linux-kernel - Re: [PATCH v2 0/2] arm64: dts: iot2050: Fix R5 lock-step settings, add overlays

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <172487125711.3441200.11079556552266288312.b4-ty@ti.com>
Date: Wed, 28 Aug 2024 13:55:18 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, Jan Kiszka
	<jan.kiszka@...mens.com>
CC: Nishanth Menon <nm@...com>, Bao Cheng Su <baocheng.su@...mens.com>,
        Hua
 Qian Li <huaqian.li@...mens.com>
Subject: Re: [PATCH v2 0/2] arm64: dts: iot2050: Fix R5 lock-step settings, add overlays

Hi Jan Kiszka,

On Wed, 28 Aug 2024 09:38:59 +0200, Jan Kiszka wrote:
> Changes in v2:
>  - build dtb with applied overlays
> 
> Trying to get our backlog closer to zero. See patches for details.
> 
> Jan
> 
> [...]

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

[1/2] arm64: dts: ti: iot2050: Disable lock-step for all iot2050 boards
      commit: e0133f883cf115d9e97e704169a9fb6003caefb2
[2/2] arm64: dts: ti: iot2050: Add overlays for M.2 used by firmware
      commit: dba27d026fc841d28a0ed373f617cc84ec0e4504

>From what I see, this seems fine, and inline with the good stuff, but if
folks feel it was a bit pre-mature to pick things up, I can drop it, but
prefer to let it cook in next for a short while if possible.

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