linux-kernel - Re: [PATCH 0/3] pinctrl: don't use gpiod_to

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:   Mon, 20 Nov 2023 16:06:43 +0100
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()

On Thu, Nov 16, 2023 at 2:43 PM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Wed, Nov 15, 2023 at 5:50 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> >
> > Let's start working towards removing gpiod_to_chip() from the kernel.
> > Start with pinctrl. The first patch should go through the GPIO tree
> > and become available through an immutable tag so that we can get more
> > conversions in this cycle elsewhere.
>
> Fair enough, maybe an immutable branch with all three patches?
> Probably best to merga all three into both subsystems I think.
>

Nah, I don't think I need to pollute the GPIO tree with every pinctrl
patch. It's enough to just merge the first one into GPIO and you do
the same in pinctrl.

Bart

> Acked-by: Linus Walleij <linus.walleij@...aro.org>
>
> Yours,
> Linus Walleij