Message ID | 20220209162607.1118325-1-maz@kernel.org |
---|---|
Headers | show |
Series | irqchip: Prevent drivers abusing irq_chip::name | expand |
On Wed, Feb 9, 2022 at 5:26 PM Marc Zyngier <maz@kernel.org> wrote: > Having done that, we can cleanup a few irqchip drivers and make their > irq_chip structure const (which requires touching a handful of core > functions). Whilst we're at it, we do the same for a couple of gpio > drivers. The series: Acked-by: Linus Walleij <linus.walleij@linaro.org> Since Bartosz is queueing GPIO patches and I am mostly playing with a baby during the daytime it's good if you also get an ACK from Bartosz on this one before applying the series. Yours, Linus Walleij
On Thu, 10 Feb 2022 23:41:25 +0000, Linus Walleij <linus.walleij@linaro.org> wrote: > > On Wed, Feb 9, 2022 at 5:26 PM Marc Zyngier <maz@kernel.org> wrote: > > > Having done that, we can cleanup a few irqchip drivers and make their > > irq_chip structure const (which requires touching a handful of core > > functions). Whilst we're at it, we do the same for a couple of gpio > > drivers. > > The series: > Acked-by: Linus Walleij <linus.walleij@linaro.org> Thanks. > Since Bartosz is queueing GPIO patches and I am mostly > playing with a baby during the daytime it's good if you also > get an ACK from Bartosz on this one before applying the > series. To be on the safe side and until I hear from Bartosz, I have dropped the GPIO patches from the branch which I'm about to push into -next. If Bartosz is happy with them, I'll add them to the mix. Otherwise, they can be taken at a later time, as there is no shortage of drivers that will need reworking once we agree on the way to resolve the irqchip fiddling in gpiolib. Have fun playing! :) M.
On Fri, Feb 11, 2022 at 8:31 AM Linus Walleij <linus.walleij@linaro.org> wrote: > On Wed, Feb 9, 2022 at 5:26 PM Marc Zyngier <maz@kernel.org> wrote: ... > Since ... I am mostly > playing with a baby during the daytime A bit of a side topic, since I need to send a PR for fixes before my vacation starts tomorrow, should I Cc my PR to that Linus as well, so he can accept it? It will contain two one-liner ID patches to pin control Intel drivers and won't conflict with anything (as far as I am aware and know).
On Tue, Feb 15, 2022 at 4:38 PM Andy Shevchenko <andy.shevchenko@gmail.com> wrote: > On Fri, Feb 11, 2022 at 8:31 AM Linus Walleij <linus.walleij@linaro.org> wrote: > > On Wed, Feb 9, 2022 at 5:26 PM Marc Zyngier <maz@kernel.org> wrote: > > ... > > > Since ... I am mostly > > playing with a baby during the daytime > > A bit of a side topic, since I need to send a PR for fixes before my > vacation starts tomorrow, should I Cc my PR to that Linus as well, so > he can accept it? > It will contain two one-liner ID patches to pin control Intel drivers > and won't conflict with anything (as far as I am aware and know). I manage the pin control stuff but at a bit slow pace, so I'll pick it up! Yours, Linus Walleij