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] [day] [month] [year] [list]
Date:   Tue, 31 Mar 2020 22:55:24 +0200
From:   Thierry Reding <thierry.reding@...il.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        kbuild test robot <lkp@...el.com>
Subject: Re: [PATCH] gpio: Avoid using pin ranges with !PINCTRL

On Tue, Mar 31, 2020 at 03:05:43PM +0200, Geert Uytterhoeven wrote:
> Hi Thierry,
> 
> Thanks for your patch!
> 
> On Mon, Mar 30, 2020 at 11:03 AM Thierry Reding
> <thierry.reding@...il.com> wrote:
> > From: Thierry Reding <treding@...dia.com>
> >
> > Do not use the struct gpio_device's .pin_ranges field if the PINCTRL
> > Kconfig symbol is not selected to avoid build failures.
> >
> > Fixes: d2fbe53a806e ("gpio: Support GPIO controllers without pin-ranges")
> 
> WARNING: Unknown commit id 'd2fbe53a806e', maybe rebased or not pulled?
> 
> Fixes: 2ab73c6d8323fa1e ("gpio: Support GPIO controllers without pin-ranges")

Yeah, it looks like I made this patch on top of my local tree but forgot
to rebase on the latest linux-next.

Thierry

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ