linux-kernel - Re: [PATCH 0/2] spi: atmel: Clean usage of DMA

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: <163797660761.2988146.6224858401999788835.b4-ty@kernel.org>
Date:   Sat, 27 Nov 2021 01:30:07 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Tudor Ambarus <tudor.ambarus@...rochip.com>
Cc:     linux-arm-kernel@...ts.infradead.org, nicolas.ferre@...rochip.com,
        linux-spi@...r.kernel.org, alexandre.belloni@...tlin.com,
        ludovic.desroches@...rochip.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] spi: atmel: Clean usage of DMA

On Thu, 25 Nov 2021 14:41:08 +0200, Tudor Ambarus wrote:
> Cleaning patches done when reading DMA code. No functional change
> expected. Tested on sama5d2_xplained with at25df321a.
> 
> Tudor Ambarus (2):
>   spi: atmel: Drop slave_config argument in atmel_spi_dma_slave_config()
>   spi: atmel: Remove setting of deprecated member of struct
>     dma_slave_config
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: atmel: Drop slave_config argument in atmel_spi_dma_slave_config()
      commit: c1b00674aab0c6950970e52c0f059756064a9e8c
[2/2] spi: atmel: Remove setting of deprecated member of struct dma_slave_config
      commit: f44a29ceb99fc99832ee1d55d7fe9c4dbf594660

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