linux-kernel - Re: [PATCH v2] spi: atmel: Fix PDC transfer setup bug

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: <163313375301.13893.52482775381403027.b4-ty@kernel.org>
Date:   Sat,  2 Oct 2021 01:16:25 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tudor.ambarus@...rochip.com, nicolas.ferre@...rochip.com,
        alexandre.belloni@...tlin.com,
        Ville Baillie <VilleB@...esnap.co.uk>,
        ludovic.desroches@...rochip.com
Cc:     Mark Brown <broonie@...nel.org>, dan.sneddon@...rochip.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH v2] spi: atmel: Fix PDC transfer setup bug

On Fri, 17 Sep 2021 07:46:11 +0000, Ville Baillie wrote:
> From 7f796c2004407f848f9ed97f406e24b9eadd74be Mon Sep 17 00:00:00 2001
> From: Ville Baillie <villeb@...esnap.co.uk>
> Date: Thu, 16 Sep 2021 14:16:46 +0000
> Subject: [PATCH v2] spi: atmel: Fix PDC transfer setup bug
> 
> Commit 5fa5e6dec762 ("spi: atmel: Switch to transfer_one transfer
> method") refactored the code and changed a conditional causing
> atmel_spi_dma_map_xfer to never be called in PDC mode. This causes the
> driver to silently fail.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: atmel: Fix PDC transfer setup bug
      commit: 75e33c55ae8fb4a177fe07c284665e1d61b02560

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