[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YffDBiITSRQQXnVh@linutronix.de>
Date: Mon, 31 Jan 2022 12:07:50 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Wolfram Sang <wsa@...nel.org>, greybus-dev@...ts.linaro.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-usb@...r.kernel.org,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Alex Elder <elder@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hans de Goede <hdegoede@...hat.com>,
Jakub Kicinski <kuba@...nel.org>,
Johan Hovold <johan@...nel.org>,
Lee Jones <lee.jones@...aro.org>,
Rui Miguel Silva <rmfrfs@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
UNGLinuxDriver@...rochip.com,
Woojung Huh <woojung.huh@...rochip.com>,
Michael Below <below@...iz.de>,
Salvatore Bonaccorso <carnil@...ian.org>
Subject: Re: [PATCH 2/7] i2c: core: Use generic_handle_irq_safe() in
i2c_handle_smbus_host_notify().
On 2022-01-27 18:11:16 [+0100], Wolfram Sang wrote:
>
> I guess you want this to go together with patch 1, so:
>
> Acked-by: Wolfram Sang <wsa@...nel.org>
>
> I agree with adding the kernel bugzilla entry at least:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=202453
>
> Probably the others which Oleksandr metioned, too.
No, they are not relevant because none of them can be reproduced on a
v5.12+ kernel or any of <v5.12 stable maintained trees.
They triggered in the past only with the `threadirqs' option on the
commandline and this has been fixed by commit
81e2073c175b8 ("genirq: Disable interrupts for force threaded handlers")
Sebastian
Powered by blists - more mailing lists