linux-kernel - Re: [PATCH 18/21] iio: Replace IRQF_ONESHOT with IRQF_NO

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <be27fa4404511cdf65a9a0f212653a7f1fcd86b6.camel@gmail.com>
Date: Wed, 28 Jan 2026 10:45:01 +0000
From: Nuno Sá <noname.nuno@...il.com>
To: Konstantin Ryabitsev <mricon@...nel.org>, Andy Shevchenko
	 <andriy.shevchenko@...el.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>, tools@...nel.org, 
	linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev, Thomas
 Gleixner	 <tglx@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>, Michael
 Hennerich	 <Michael.Hennerich@...log.com>, Puranjay Mohan
 <puranjay@...nel.org>,  Jonathan Cameron	 <jic23@...nel.org>, David Lechner
 <dlechner@...libre.com>, Nuno Sá	 <nuno.sa@...log.com>,
 Andy Shevchenko <andy@...nel.org>, Marcelo Schmitt	
 <marcelo.schmitt@...log.com>, Marcus Folkesson
 <marcus.folkesson@...il.com>,  Kent Gustavsson	 <kent@...oris.se>, Gustavo
 Silva <gustavograzs@...il.com>, Nishant Malpani	
 <nish.malpani25@...il.com>, linux-iio@...r.kernel.org
Subject: Re: [PATCH 18/21] iio: Replace IRQF_ONESHOT with IRQF_NO_THREAD

On Mon, 2026-01-26 at 09:29 -0500, Konstantin Ryabitsev wrote:
> On Mon, Jan 26, 2026 at 01:01:02PM +0200, Andy Shevchenko wrote:
> > > I lose it on the next if I update patches in tree and re-export them. 
> > 
> > I don't understand this, sorry. Can you provide a step-by-step example?
> > Do you mean that you are taking previous version from the list and reapplying
> > it via `git am`? But shouldn't `b4` take care of that as long as it knows the
> > Change-ID and it matches?
> 
> That's not the intended workflow -- the series is kept as a branch in your
> local tree and any updates happen to that branch, so any entries in a commit
> falling under "---" will persist across revisions.
> 

Hi Konstantin,

Since I have you here, I might ask about something that I'm not sure how to handle. Might be dumb
but here it goes. One problem is when I send v1 based on a branch and when I'm starting to work on
v2 that branch was force-updated and I want to base my v2 on it. Is there any good way to handle
this?


What I currently do is more or less:

git cat-file -p $COVER_SHA
git reset --hard origin/branch
git commit --allow-empty (and past all the cover with b4 metadata)
// apply my series patches.

Thx!
- Nuno Sá
>