[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260126092523.jm0QzgTW@linutronix.de>
Date: Mon, 26 Jan 2026 10:25:23 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev,
Thomas Gleixner <tglx@...nel.org>,
Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>,
Nuno Sá <nuno.sa@...log.com>,
Andy Shevchenko <andy@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Michael Hennerich <Michael.Hennerich@...log.com>,
linux-iio@...r.kernel.org
Subject: Re: [PATCH 19/21] iio: Use IRQF_NO_THREAD
On 2026-01-23 16:50:58 [+0200], Andy Shevchenko wrote:
> > ret = request_irq(st->i2c->irq,
> > &iio_trigger_generic_data_rdy_poll,
> > - IRQF_TRIGGER_RISING,
> > + IRQF_NO_THREAD | IRQF_TRIGGER_RISING,
>
> Maybe swap their positions as it's done everywhere else for the consistency's
> sake?
Almost missed this. I swapped the flags, re-ident-ed.
Also updated the commit message that ad7766_irq() is identical to
iio_trigger_generic_data_rdy_poll() and can be replaced. Hope that works
for everyone.
> > "itg3200_data_rdy",
> > st->trig);
Sebastian
Powered by blists - more mailing lists