From: Thierry Reding <thierry.reding@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH] gpio: Avoid using pin ranges with !PINCTRL
Date: Tue, 31 Mar 2020 22:55:24 +0200 [thread overview]
Message-ID: <20200331205524.GE2954599@ulmo> (raw)
In-Reply-To: <CAMuHMdXiK3KLU1=s4ykxmUVSsgwbnnc476w=Nnj-HsVytK2Lqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
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@gmail.com> wrote:
> > From: Thierry Reding <treding@nvidia.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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-31 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 9:02 [PATCH] gpio: Avoid using pin ranges with !PINCTRL Thierry Reding
2020-03-31 13:05 ` Geert Uytterhoeven
2020-03-31 20:55 ` Thierry Reding [this message]
2020-03-31 14:48 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200331205524.GE2954599@ulmo \
--to=thierry.reding@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.