linux-kernel - Re: [PATCH 0/2] spi: offload: fixes

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: <173938676238.250565.8485583434084673680.b4-ty@kernel.org>
Date: Wed, 12 Feb 2025 18:59:22 +0000
From: Mark Brown <broonie@...nel.org>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>, 
 Nuno Sa <nuno.sa@...log.com>, David Lechner <dlechner@...libre.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Stephen Rothwell <sfr@...b.auug.org.au>, kernel test robot <lkp@...el.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: [PATCH 0/2] spi: offload: fixes

On Wed, 12 Feb 2025 11:33:11 -0600, David Lechner wrote:
> Fix a couple of issues that were reported with the recently added SPI
> offload series.
> 
> 

Applied to

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

Thanks!

[1/2] spi: fix missing offload_flags doc
      commit: d795a052b0ddad3da83dda6ff522c1b1aaa4a525
[2/2] spi: offload: fix use after free
      commit: e957c96455e8f4c630d5e374312cad0633ca7e17

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