linux-kernel - Re: [PATCH v4 1/1] spi: offload: Add offset parameter

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: <176053044658.105519.915414342804429574.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 13:14:06 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-iio@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Marcelo Schmitt <marcelo.schmitt@...log.com>
Cc: Axel Haslam <ahaslam@...libre.com>, jic23@...nel.org, 
 nuno.sa@...log.com, dlechner@...libre.com, andy@...nel.org, 
 marcelo.schmitt1@...il.com
Subject: Re: [PATCH v4 1/1] spi: offload: Add offset parameter

On Mon, 06 Oct 2025 11:25:41 -0300, Marcelo Schmitt wrote:
> Add an offset parameter that can be passed in the periodic trigger.
> This is useful for example when ADC drivers implement a separate periodic
> signal to trigger conversion and need offload to read the result with
> some delay. While at it, add some documentation to offload periodic trigger
> parameters.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: offload: Add offset parameter
      commit: b83fb1b14c06bdd765903ac852ba20a14e24f227

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