On Mon, May 23, 2022 at 9:25 AM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > Hi Bartosz, > > On Sun, May 22, 2022 at 10:13 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > On Fri, May 20, 2022 at 12:23 PM Geert Uytterhoeven > > <geert+renesas@xxxxxxxxx> wrote: > > > Commit 6c846d026d49 ("gpio: Don't fiddle with irqchips marked as > > > immutable") added a warning to indicate if the gpiolib is altering the > > > internals of irqchips. Following this change the following warning is > > > now observed for the dwapb driver: > > > > > > gpio gpiochip0: (50200000.gpio): not an immutable chip, please consider fixing it! > > > > > > Fix this by making the irqchip in the dwapb driver immutable. > > > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > > --- > > > Against gpio/for-next. > > > Boot-tested on SiPEED MAiXBiT (Canaan K210). > > > > > > v2: > > > - Factor out hwirq using preferred helper. > > > I'll pick those patches up for the next cycle to let them spend some > > time in next. > > "next cycle" = later PR for v5.19, I hope? > If the new warning will make it into v5.19-rc1 (commit 6c846d026d490b23 > is in gpio/for-next), I think you should collect all fixes and make > sure they end up in v5.19, too. > Ah you're right, sorry, yeah I will pick those up now. Bart