[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXiK3KLU1=s4ykxmUVSsgwbnnc476w=Nnj-HsVytK2Lqg@mail.gmail.com>
Date: Tue, 31 Mar 2020 15:05:43 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Thierry Reding <thierry.reding@...il.com>
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
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")
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Reported-by: kbuild test robot <lkp@...el.com>
> Signed-off-by: Thierry Reding <treding@...dia.com>
With the above fixed:
Reviewed-by: Geert Uytterhoeven <geert@...ux-m68k.org>
This fixes the build (and boot) for rbtx4927, so:
Tested-by: Geert Uytterhoeven <geert@...ux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists