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: <176192142799.427883.12507657912485328517.b4-ty@ti.com>
Date: Fri, 31 Oct 2025 20:10:57 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <praneeth@...com>, Paresh Bhagat <p-bhagat@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <kristo@...nel.org>,
	<robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <khasim@...com>, <v-singh1@...com>,
	<afd@...com>, <bb@...com>, <s-k6@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62d2-evm: Remove unused ospi0 chip select pins

Hi Paresh Bhagat,

On Wed, 29 Oct 2025 08:51:44 +0530, Paresh Bhagat wrote:
> Since only a single flash device is connected to ospi0 retain only the
> OSPI0_CSn0 pin configuration and remove the unused CSn1-CSn3 pins from
> the default pinctrl. This simplifies the ospi0 pin configuration without
> affecting functionality.
> 
> 

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

[1/1] arm64: dts: ti: k3-am62d2-evm: Remove unused ospi0 chip select pins
      commit: da84d094ded6e332c88c67218faabfbf8d3d59e5

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