linux-kernel - Re: [PATCH 0/2] Set boot tags for the usb0 port of AM62x SK and Beagleplay

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: <170719349980.2245010.13978940073133357464.b4-ty@ti.com>
Date: Tue, 6 Feb 2024 09:59:10 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <linux-arm-kernel@...ts.infradead.org>,
        Sjoerd Simons
	<sjoerd@...labora.com>
CC: Vignesh Raghavendra <vigneshr@...com>, <kernel@...labora.com>,
        Conor
 Dooley <conor+dt@...nel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>,
        Nishanth Menon <nm@...com>, Rob Herring
	<robh+dt@...nel.org>,
        Tero Kristo <kristo@...nel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] Set boot tags for the usb0 port of AM62x SK and Beagleplay

Hi Sjoerd Simons,

On Fri, 12 Jan 2024 10:17:06 +0100, Sjoerd Simons wrote:
> The AM62x SoC can be booted from the first USB port using DFU. Set the
> relevant boot tags for both
> 
> 
> Sjoerd Simons (2):
>   arm64: dts: ti: k3-am625-sk: Add boot phase tags for USB0
>   arm64: dts: ti: k3-am625-beagleplay: Add boot phase tags for USB0
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am625-sk: Add boot phase tags for USB0
      commit: 524c8086a453b8df1002c1ccfa9f99589761fc80
[2/2] arm64: dts: ti: k3-am625-beagleplay: Add boot phase tags for USB0
      commit: f7d2844d848f8836e6a7923e3ea426f7be4f38d1

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