Message ID | 20220211181500.1856198-3-bigeasy@linutronix.de |
---|---|
State | Accepted |
Commit | 68ea1b2c3386ad484b7daa4a64fa7b3be661607f |
Headers | show |
Series | Provide and use generic_handle_irq_safe() where appropriate. | expand |
On 2022-02-23 14:21:32 [+0100], Wolfram Sang wrote:
> Is this 5.17 material? Or is 5.18 fine, too?
5.18 is fine. I intend to push into the RT-stable trees and this can't
be backported without 1/7 and it does not affect !RT so I wouldn't
bother.
Sebastian
On Fri, Feb 25, 2022 at 11:26:46PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-02-23 14:21:32 [+0100], Wolfram Sang wrote: > > Is this 5.17 material? Or is 5.18 fine, too? > > 5.18 is fine. I intend to push into the RT-stable trees and this can't > be backported without 1/7 and it does not affect !RT so I wouldn't > bother. Ok, applied to for-next then. Thanks for the heads up!
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c index 2c59dd748a49f..3f9e5303b6163 100644 --- a/drivers/i2c/i2c-core-base.c +++ b/drivers/i2c/i2c-core-base.c @@ -1424,7 +1424,7 @@ int i2c_handle_smbus_host_notify(struct i2c_adapter *adap, unsigned short addr) if (irq <= 0) return -ENXIO; - generic_handle_irq(irq); + generic_handle_irq_safe(irq); return 0; }