linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Marcelo Schmitt <marcelo.schmitt@analog.com>,
	Axel Haslam <ahaslam@baylibre.com>,
	nuno.sa@analog.com, dlechner@baylibre.com, andy@kernel.org,
	marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v4 1/1] spi: offload: Add offset parameter
Date: Sat, 18 Oct 2025 14:13:41 +0100	[thread overview]
Message-ID: <20251018141341.3ef2f6b7@jic23-huawei> (raw)
In-Reply-To: <176053044658.105519.915414342804429574.b4-ty@kernel.org>

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.

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
> 


  reply	other threads:[~2025-10-18 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 14:25 [PATCH v4 1/1] spi: offload: Add offset parameter Marcelo Schmitt
2025-10-15 12:14 ` Mark Brown
2025-10-18 13:13   ` Jonathan Cameron [this message]
2025-10-27 13:53     ` Jonathan Cameron
2025-11-03 15:33 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251018141341.3ef2f6b7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=ahaslam@baylibre.com \
    --cc=andy@kernel.org \
    --cc=broonie@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=marcelo.schmitt@analog.com \
    --cc=nuno.sa@analog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).