lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 15 Feb 2022 12:13:55 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>, linux-kernel@...r.kernel.org,
        linux-gpio@...r.kernel.org,
        Matthias Brugger <matthias.bgg@...il.com>,
        Grygorii Strashko <grygorii.strashko@...com>,
        Santosh Shilimkar <ssantosh@...nel.org>,
        Kevin Hilman <khilman@...nel.org>,
        Tony Lindgren <tony@...mide.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Vladimir Zapolskiy <vz@...ia.com>,
        Andrew Lunn <andrew@...n.ch>,
        Gregory Clement <gregory.clement@...tlin.com>,
        Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
        Emil Renner Berthing <kernel@...il.dk>,
        kernel-team@...roid.com
Subject: Re: [PATCH 00/10] irqchip: Prevent drivers abusing irq_chip::name

On Thu, 10 Feb 2022 23:41:25 +0000,
Linus Walleij <linus.walleij@...aro.org> wrote:
> 
> On Wed, Feb 9, 2022 at 5:26 PM Marc Zyngier <maz@...nel.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@...aro.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.

-- 
Without deviation from the norm, progress is not possible.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ