Message ID | 3712e871-bf2f-32c5-f9c2-2968c42087f8@omp.ru (mailing list archive) |
---|---|
Headers | show |
Series | Correctly handle plaform_get_irq()'s result in the i2C drivers | expand |
On 7/4/21 5:32 PM, Sergey Shtylyov wrote: > Here are 5 patches against the 'i2c/for-current' branch of Wolfram's 'linux.git' repo. > The affected drivers call platform_get_irq() but mis-interprete its result -- they consider > IRQ0 as error and (sometimes) the real error codes as valid IRQs... :-/ > > [1/5] i2c: hix5hd2: fix IRQ check > [2/5] i2c: mt65xx: fix IRQ check > [3/5] i2c: pmcmsp: fix IRQ check > [4/5] i2c: s3c2410: fix IRQ check > [5/5] i2c: xlp9xx: fix main IRQ check Wolfram, hat's up with this series (its status in the patchwork is still "new")? MBR, Sergey
On 8/11/21 11:12 PM, Sergey Shtylyov wrote: >> Here are 5 patches against the 'i2c/for-current' branch of Wolfram's 'linux.git' repo. >> The affected drivers call platform_get_irq() but mis-interprete its result -- they consider >> IRQ0 as error and (sometimes) the real error codes as valid IRQs... :-/ >> >> [1/5] i2c: hix5hd2: fix IRQ check >> [2/5] i2c: mt65xx: fix IRQ check >> [3/5] i2c: pmcmsp: fix IRQ check >> [4/5] i2c: s3c2410: fix IRQ check >> [5/5] i2c: xlp9xx: fix main IRQ check > > Wolfram, hat's up with this series (its status in the patchwork is still "new")? What's, of/c. :-) MBR, Sergey