linux-kernel - Re: [PATCH] spi: spi_amd: Add support for SPI MEM framework

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: <171145676359.65249.16490947965037901357.b4-ty@kernel.org>
Date: Tue, 26 Mar 2024 12:39:23 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Raju Rangoju <Raju.Rangoju@....com>
Cc: sanju.mehta@....com, linux-kernel@...r.kernel.org, 
 Sudheesh Mavila <sudheesh.mavila@....com>, 
 Krishnamoorthi M <krishnamoorthi.m@....com>, 
 Akshata MukundShetty <akshata.mukundshetty@....com>
Subject: Re: [PATCH] spi: spi_amd: Add support for SPI MEM framework

On Thu, 29 Feb 2024 19:15:44 +0530, Raju Rangoju wrote:
> Add support to the SPI controller driver to use SPI MEM framework.
> SPI subsystem utilizing the SPI memory operations allows to re-use
> SPI controller drivers for both SPI NOR devices, regular SPI devices
> as well as SPI NAND devices.
> 
> Add below functions of spi_mem_ops to support SPI MEM framework
> - exec-op(): to execute the memory operations.
> - supports_op(): to check if the memory operation is supported.
> - adjust_op_size(): to split data transfers so that they don’t exceed the
>   max transfer size supported by the controller.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi_amd: Add support for SPI MEM framework
      commit: 6defadbe6cbc3a87dc39c119a6748d19bfba0544

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