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]
Message-ID: <171984950185.3152309.13270720287525957044.b4-ty@ti.com>
Date: Wed, 3 Jul 2024 10:09:21 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Dhruva Gole <d-gole@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, Roger Quadros <rogerq@...nel.org>,
        Andrew
 Davis <afd@...com>, Tero Kristo <kristo@...nel.org>
Subject: Re: [RFT][PATCH 0/2] dts: ti: Fix build warns in usb@...00000

Hi Dhruva Gole,

On Wed, 26 Jun 2024 15:45:18 +0530, Dhruva Gole wrote:
> The series has been marked as RFT because although I was able to boot
> test, it needs to be made sure that usb features aren't affected by this
> change. Ideally, looking at the driver, I don't think it really is
> looking at port@X but incase I missed anything please feel free to point
> out.
> 
> I'm working on top of tag: next-20240625
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am62p5-sk: fix graph_child_address warnings
      commit: 28a950c404679aba602e3311c733a19b7c945ab4
[2/2] arm64: dts: ti: k3-am62x-sk-common: Fix graph_child_address warns
      commit: cf645197f045147cd0232c7a205cdfed49590756

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ