linux-kernel - Re: [PATCH v3 SPI for-next 0/3] DMA Support for SPI in PCI1xxxx

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: <170742731351.2266792.10091004097755614677.b4-ty@kernel.org>
Date: Thu, 08 Feb 2024 21:21:53 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Thangaraj Samynathan <thangaraj.s@...rochip.com>
Cc: UNGLinuxDriver@...rochip.com, kumaravel.thiagarajan@...rochip.com, 
 tharunkumar.pasumarthi@...rochip.com
Subject: Re: [PATCH v3 SPI for-next 0/3] DMA Support for SPI in PCI1xxxx

On Wed, 07 Feb 2024 13:36:19 +0530, Thangaraj Samynathan wrote:
> This series of patch is to add DMA Support that improves SPI Performance
> in PCI1xxxx. With DMA Support in 20MHz clock, the performance is
> improved from 6Mbps to 17Mbps.
> 
> v3:
> -Merged Tx and Rx DMA patches into one to avoid unidirectional dma.
> -Changed naming from DMA read and write functions to from_io and to_io
> to avoid confusion between DMA and SPI Controller operations.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: mchp-pci1xxxx: Add support for DMA in SPI
      commit: 3e7cfd6ad29a7483ce3addebb4fba87d6409c71c
[2/2] spi: mchp-pci1xxxx: DMA support for copying data to and from SPI Buf
      commit: 9538edeb72c989a4b90964ae4bba107eaf21a791

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