linux-kernel - Re: [PATCH v3 0/2] spi: aspeed: Improve handling of shared SPI controllers

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <176960558580.1648911.5452842376187241181.b4-ty@kernel.org>
Date: Wed, 28 Jan 2026 13:06:25 +0000
From: Mark Brown <broonie@...nel.org>
To: clg@...d.org, joel@....id.au, andrew@...econstruct.com.au, 
 linux-aspeed@...ts.ozlabs.org, openbmc@...ts.ozlabs.org, 
 linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, BMC-SW@...eedtech.com, pmenzel@...gen.mpg.de, 
 Boris Brezillon <bbrezillon@...nel.org>, 
 Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
Subject: Re: [PATCH v3 0/2] spi: aspeed: Improve handling of shared SPI
 controllers

On Tue, 20 Jan 2026 20:30:03 +0800, Chin-Ting Kuo wrote:
> This patch series improves handling of SPI controllers that are
> shared by spi-mem devices and other SPI peripherals.
> 
> The primary goal of this series is to support non-spi-mem devices in
> the ASPEED FMC/SPI controller driver. It also addresses an issue in
> the spi-mem framework observed when different types of SPI devices
> operate concurrently on the same controller, ensuring that spi-mem
> operations are properly serialized.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] spi: spi-mem: Protect dirmap_create() with spi_mem_access_start/end
      commit: 53f826ff5e0e3ecb279862ca7cce1491b94bb017
[2/2] spi: aspeed: Add support for non-spi-mem devices
      commit: 04f7516ab70f7b82aae1d2830af2ee6f17f3fe98

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a 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.

Thanks,
Mark