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: <175766786999.26286.12984291959565660129.b4-ty@ti.com>
Date: Fri, 12 Sep 2025 04:50:41 -0500
From: Nishanth Menon <nm@...com>
To: Judith Mendez <jm@...com>
CC: Nishanth Menon <nm@...com>, Moteen Shah <m-shah@...com>,
        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>,
        Andrew Davis <afd@...com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] Remove HS400 support from common

Hi Judith Mendez,

On Mon, 08 Sep 2025 18:52:05 -0500, Judith Mendez wrote:
> Since eMMC HS400 has been descoped for j722s due to errata i2478 [0]
> and is supported by default for AM62Px device, remove sdhci0 node from
> common-main.dtsi and include instead only for AM62Px in am62p-main.dtsi.
> 
> Also, update the STRB value for am62p eMMC sdhci0 node.
> 
> Tested on am62p SK board.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am62p/j722s: Remove HS400 support from common
      commit: 7efc354b7fe1ac5e874d0188b3d6be88a3fa0fe4
[2/2] arm64: dts: ti: k3-am62p: Update eMMC HS400 STRB value
      commit: 9fdcc5f98141cf2f77e8778bee830190d7b71ced

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
https://ti.com/opensource


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ