public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	tools@kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Puranjay Mohan" <puranjay@kernel.org>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
	"Marcus Folkesson" <marcus.folkesson@gmail.com>,
	"Kent Gustavsson" <kent@minoris.se>,
	"Gustavo Silva" <gustavograzs@gmail.com>,
	"Nishant Malpani" <nish.malpani25@gmail.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 18/21] iio: Replace IRQF_ONESHOT with IRQF_NO_THREAD
Date: Mon, 26 Jan 2026 10:09:25 -0500	[thread overview]
Message-ID: <20260126-delectable-utopian-oriole-5418c6@lemur> (raw)
In-Reply-To: <aXeA1AIcOx7yUNaz@smile.fi.intel.com>

On Mon, Jan 26, 2026 at 04:57:24PM +0200, Andy Shevchenko wrote:
> What I have i mind is rather the scenario when I see already sent (by somebody
> else) patch in the mailing list and I want develop a followup with the same
> To/Cc list. So I want `b4 ... --use/restore-to-cc-from-the-mailing-list / lore`
> type of functionality.

To understand it better -- you want to send a new revision to a patch sent by
someone else? If so, you should be able to "b4 prep --from-thread <msgid>",
but it's actually a good question if that will do the right thing with content
under "---" or not, as I'm not sure this part was ever properly tested.

-K

  reply	other threads:[~2026-01-26 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260123113708.416727-1-bigeasy@linutronix.de>
     [not found] ` <20260123113708.416727-19-bigeasy@linutronix.de>
     [not found]   ` <aXOKVqxyhQ10l9V4@smile.fi.intel.com>
     [not found]     ` <20260126081510.jr8Rp6R7@linutronix.de>
     [not found]       ` <aXc5Efu-PlLNCxkk@smile.fi.intel.com>
     [not found]         ` <20260126101034.lnGGQmUD@linutronix.de>
2026-01-26 11:01           ` [PATCH 18/21] iio: Replace IRQF_ONESHOT with IRQF_NO_THREAD Andy Shevchenko
2026-01-26 14:29             ` Konstantin Ryabitsev
2026-01-26 14:57               ` Andy Shevchenko
2026-01-26 15:09                 ` Konstantin Ryabitsev [this message]
2026-01-26 15:16                   ` Andy Shevchenko
2026-01-28 10:45               ` Nuno Sá
2026-01-28 13:53                 ` Konstantin Ryabitsev
2026-01-28 10:07             ` Sebastian Andrzej Siewior
2026-01-28 10:15               ` Andy Shevchenko

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=20260126-delectable-utopian-oriole-5418c6@lemur \
    --to=mricon@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=dlechner@baylibre.com \
    --cc=gustavograzs@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kent@minoris.se \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=marcelo.schmitt@analog.com \
    --cc=marcus.folkesson@gmail.com \
    --cc=nish.malpani25@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=puranjay@kernel.org \
    --cc=tglx@kernel.org \
    --cc=tools@kernel.org \
    /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