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

[Jonathan Cameron <jic23@kernel.org>]

On Sat, 18 Oct 2025 14:13:41 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> On Wed, 15 Oct 2025 13:14:06 +0100
> Mark Brown <broonie@kernel.org> wrote:
> 
> > 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
> >   
> Hi Mark,
> 
> The patch called out that we are after an immutable branch or similar for this one.
> 
> "
> Hello,
> 
> This patch adds a small feature that is required for a series improving ad4030
> in the IIO subsystem [1]. Can we have an immutable branch with this patch so
> that it can be used as base for the IIO driver changes?
> 
> [1]: https://lore.kernel.org/linux-iio/cover.1758916484.git.marcelo.schmitt@analog.com/
> "
> 
> If you can still set that up, much appreciated.
Hi Mark,

The ad4030 changes are stuck on resolving this or waiting a cycle :(
If you get a chance to take a look and maybe merge it a different way that would be great.

Thanks,

Jonathan

> 
> Thanks,
> 
> Jonathan
> 
> > 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
> >   
> 
>