From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
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: Mon, 16 Oct 2017 10:08:21 +0200 [thread overview]
Message-ID: <20171016080821.GC17369@ulmo> (raw)
In-Reply-To: <20171016080502.GB17369@ulmo>
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
On Mon, Oct 16, 2017 at 10:05:02AM +0200, Thierry Reding wrote:
> On Sun, Oct 15, 2017 at 04:21:14PM +0200, Linus Walleij wrote:
> > Grygorii, can you look at this?
> >
> > Linus
> >
> > On Sun, Oct 15, 2017 at 3:52 AM, kbuild test robot
> > <fengguang.wu@intel.com> wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
> > > head: be58c675d634e0b91edc0f721c77303ac2afa809
> > > commit: be58c675d634e0b91edc0f721c77303ac2afa809 [12/12] gpiolib: drop irq_base field from gpio_chip struct
> > > config: arm64-defconfig (attached as .config)
> > > compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> > > reproduce:
> > > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > > chmod +x ~/bin/make.cross
> > > git checkout be58c675d634e0b91edc0f721c77303ac2afa809
> > > # save the attached .config to linux build tree
> > > make.cross ARCH=arm64
> > >
> > > All errors (new ones prefixed by >>):
> > >
> > > drivers/pinctrl/mvebu/pinctrl-armada-37xx.c: In function 'armada_37xx_irq_startup':
> > >>> drivers/pinctrl/mvebu/pinctrl-armada-37xx.c:630:27: error: 'struct gpio_chip' has no member named 'irq_base'; did you mean 'base'?
> > > int irq = d->hwirq - chip->irq_base;
>
> This looks like something you'd get if you merge my struct
> gpio_irq_chip patches. However, the patch in my series will do the
> conversion of the pinctrl-armada-37xx driver:
>
> --- >8 ---
> $ git log -p -- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c
> commit 96e359456c942969fc3f0faa277fb27d1a830692
> Author: Thierry Reding <treding@nvidia.com>
> Date: Mon Apr 3 11:40:03 2017 +0200
>
> gpio: Move irq_base to struct gpio_irq_chip
>
> In order to consolidate the multiple ways to associate an IRQ chip with
> a GPIO chip, move more fields into the new struct gpio_irq_chip.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> diff --git a/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c b/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c
> index c9851bd120b4..500238d898ea 100644
> --- a/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c
> +++ b/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c
> @@ -627,7 +627,7 @@ static void armada_37xx_irq_handler(struct irq_desc *desc)
> static unsigned int armada_37xx_irq_startup(struct irq_data *d)
> {
> struct gpio_chip *chip = irq_data_get_irq_chip_data(d);
> - int irq = d->hwirq - chip->irq_base;
> + int irq = d->hwirq - chip->irq.first;
> /*
> * The mask field is a "precomputed bitmask for accessing the
> * chip registers" which was introduced for the generic
Nevermind, I see there is now yet another conflict that would require
yet another rebase of that series.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-16 8:08 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 [this message]
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
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=20171016080821.GC17369@ulmo \
--to=thierry.reding@gmail.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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).