From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [gpio:devel 12/12] drivers/pinctrl/mvebu/pinctrl-armada-37xx.c:630:27: error: 'struct gpio_chip' has no member named 'irq_base'; did you mean 'base'?
Date: Thu, 19 Oct 2017 13:16:40 +0200 [thread overview]
Message-ID: <87zi8n5qw7.fsf@free-electrons.com> (raw)
In-Reply-To: <CACRpkdYyq0vw=9H2xRg1W4LVvdyc_m1-Mayo=ZvtB+_BQTrhjQ@mail.gmail.com> (Linus Walleij's message of "Mon, 16 Oct 2017 23:15:57 +0200")
Hi Linus and Thierry,
On lun., oct. 16 2017, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Mon, Oct 16, 2017 at 4:53 PM, Gregory CLEMENT
> <gregory.clement@free-electrons.com> wrote:
>
>> Thanks for adding me in CC I wonder why I was not in CC in the original
>> series whereas we properly fill the MAINTAINER file for this.
>
> Because the change causing this was not touching any Armada
> files.
>
> It is a fallout from the driver using gpiolib
> internals. (chip->irq_base).
OK I see.
About the patch itself I tested it on the Armada 3720 DB and it's OK for
me:
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
>
> Yours,
> Linus Walleij
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-10-19 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 1:52 [gpio:devel 12/12] drivers/pinctrl/mvebu/pinctrl-armada-37xx.c:630:27: error: 'struct gpio_chip' has no member named 'irq_base'; did you mean 'base'? kbuild test robot
2017-10-15 14:21 ` Linus Walleij
2017-10-16 8:05 ` Thierry Reding
2017-10-16 8:08 ` Thierry Reding
2017-10-16 11:50 ` Linus Walleij
2017-10-16 12:46 ` Thierry Reding
2017-10-16 14:53 ` Gregory CLEMENT
2017-10-16 21:15 ` Linus Walleij
2017-10-19 11:16 ` Gregory CLEMENT [this message]
2017-10-19 13:17 ` 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=87zi8n5qw7.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=fengguang.wu@intel.com \
--cc=grygorii.strashko@ti.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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.