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

Message-Id: <c064a31a-a2c7-4e35-b8d6-063684f48869@app.fastmail.com>
Date: Wed, 28 Jan 2026 08:53:58 -0500
From: "Konstantin Ryabitsev" <mricon@...nel.org>
To: Nuno Sá <noname.nuno@...il.com>,
 "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 Wed, Jan 28, 2026, at 05:45, Nuno Sá wrote:
> 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?

You should be able to just rebase the b4 branch.

git switch b4/your-branch
git rebase tracking-branch

You can do this at any point, not necessarily between revisions. Since we have the tracking empty commit, we'll always know the base-commit automatically.

-K