linux-kernel - Re: (subset) [PATCH v2 0/2] spi: add devm_spi_optimize

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: <171934116763.1172279.176434160030643292.b4-ty@kernel.org>
Date: Tue, 25 Jun 2024 19:46:07 +0100
From: Mark Brown <broonie@...nel.org>
To: Jonathan Cameron <jic23@...nel.org>, 
 David Lechner <dlechner@...libre.com>
Cc: Michael Hennerich <michael.hennerich@...log.com>, 
 Nuno Sá <nuno.sa@...log.com>, 
 Marcelo Schmitt <marcelo.schmitt@...log.com>, 
 Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org, 
 linux-iio@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/2] spi: add devm_spi_optimize_message()
 helper

On Mon, 24 Jun 2024 15:10:29 -0500, David Lechner wrote:
> In the IIO subsystem, we are finding that it is common to call
> spi_optimize_message() during driver probe since the SPI message
> doesn't change for the lifetime of the driver. This patch adds a
> devm_spi_optimize_message() helper to simplify this common pattern.
> 

Applied to

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

Thanks!

[1/2] spi: add EXPORT_SYMBOL_GPL(devm_spi_optimize_message)
      commit: 7e74a45c7afdd8a9f82d14fd79ae0383bbaaed1e

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