All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Joel Stanley <joel@jms.id.au>, Arnd Bergmann <arnd@arndb.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 3/5] ARM: SoC changes for v5.9
Date: Tue, 4 Aug 2020 09:55:40 +0200	[thread overview]
Message-ID: <CACRpkdY+qb-d31cZjWtscSOMLxdvyaHc5xFbTd-k8AA0_fTXUg@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Vc8yXqCsZ79=YWZLJ3ObgA1AYLj0eqqK0e8sXvMWsf+Hg@mail.gmail.com>

On Tue, Aug 4, 2020 at 9:34 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Tue, Aug 4, 2020 at 10:02 AM Joel Stanley <joel@jms.id.au> wrote:
> >
> > On Mon, 3 Aug 2020 at 21:49, Arnd Bergmann <arnd@arndb.de> wrote:
> > > ARM: SoC changes for v5.9
> >
> > > Andy Shevchenko (1):
> > >       ARM: orion/gpio: Make use of for_each_requested_gpio()
> >
> > This change broke the arm build (I noticed it when building multi_v5_defconfig):
> >
> > ../arch/arm/plat-orion/gpio.c:457:2: error: implicit declaration of
> > function ‘for_each_requested_gpio’
> > [-Werror=implicit-function-declaration]
> >   457 |  for_each_requested_gpio(chip, i, label) {
> >       |  ^~~~~~~~~~~~~~~~~~~~~~~
> >
> > for_each_requested_gpio isn't in Linus (Torvalds) tree yet. It will be
> > fixed when he pulls Linus Walleij's GPIO tree which has the commit:
> >
> >  b3337eb24831 gpiolib: Introduce for_each_requested_gpio_in_range() macro
>
> Linus W. specifically created an immutable branch [1] for this.
> And I think I commented somewhere that entire branch should be pulled.

OK let's fix it by firing off the GPIO pull request ASAP.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SoC Team <soc@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 3/5] ARM: SoC changes for v5.9
Date: Tue, 4 Aug 2020 09:55:40 +0200	[thread overview]
Message-ID: <CACRpkdY+qb-d31cZjWtscSOMLxdvyaHc5xFbTd-k8AA0_fTXUg@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Vc8yXqCsZ79=YWZLJ3ObgA1AYLj0eqqK0e8sXvMWsf+Hg@mail.gmail.com>

On Tue, Aug 4, 2020 at 9:34 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Tue, Aug 4, 2020 at 10:02 AM Joel Stanley <joel@jms.id.au> wrote:
> >
> > On Mon, 3 Aug 2020 at 21:49, Arnd Bergmann <arnd@arndb.de> wrote:
> > > ARM: SoC changes for v5.9
> >
> > > Andy Shevchenko (1):
> > >       ARM: orion/gpio: Make use of for_each_requested_gpio()
> >
> > This change broke the arm build (I noticed it when building multi_v5_defconfig):
> >
> > ../arch/arm/plat-orion/gpio.c:457:2: error: implicit declaration of
> > function ‘for_each_requested_gpio’
> > [-Werror=implicit-function-declaration]
> >   457 |  for_each_requested_gpio(chip, i, label) {
> >       |  ^~~~~~~~~~~~~~~~~~~~~~~
> >
> > for_each_requested_gpio isn't in Linus (Torvalds) tree yet. It will be
> > fixed when he pulls Linus Walleij's GPIO tree which has the commit:
> >
> >  b3337eb24831 gpiolib: Introduce for_each_requested_gpio_in_range() macro
>
> Linus W. specifically created an immutable branch [1] for this.
> And I think I commented somewhere that entire branch should be pulled.

OK let's fix it by firing off the GPIO pull request ASAP.

Yours,
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-08-04  7:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 21:34 [GIT PULL 0/5] ARM: SoC: changes for v5.9 Arnd Bergmann
2020-08-03 21:34 ` Arnd Bergmann
2020-08-03 21:36 ` [GIT PULL 1/5] ARM: defconfig updates " Arnd Bergmann
2020-08-03 21:36   ` Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:44 ` [GIT PULL 2/5] ARM: SoC: DT changes " Arnd Bergmann
2020-08-03 21:44   ` Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:47 ` [GIT PULL 3/5] ARM: SoC " Arnd Bergmann
2020-08-03 21:47   ` Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-04  7:02   ` Joel Stanley
2020-08-04  7:02     ` Joel Stanley
2020-08-04  7:33     ` Andy Shevchenko
2020-08-04  7:33       ` Andy Shevchenko
2020-08-04  7:39       ` Andy Shevchenko
2020-08-04  7:39         ` Andy Shevchenko
2020-08-04  7:55       ` Linus Walleij [this message]
2020-08-04  7:55         ` Linus Walleij
2020-08-04 18:38     ` Linus Torvalds
2020-08-04 18:38       ` Linus Torvalds
2020-08-03 21:49 ` [GIT PULL 4/5] ARM: SoC driver updates " Arnd Bergmann
2020-08-03 21:49   ` Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:50 ` [GIT PULL 5/5] ARM: new SoC support " Arnd Bergmann
2020-08-03 21:50   ` Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-05 17:27 ` [GIT PULL 0/5] ARM: SoC: changes " Pavel Machek
2020-08-05 17:27   ` Pavel Machek
2020-08-05 19:06   ` Arnd Bergmann
2020-08-05 19:06     ` Arnd Bergmann
2020-08-05 19:28     ` Konrad Dybcio
2020-08-05 19:28       ` Konrad Dybcio
2020-08-05 19:45       ` Pavel Machek
2020-08-05 19:45         ` Pavel Machek
2020-08-05 19:58         ` Konrad Dybcio
2020-08-05 19:58           ` Konrad Dybcio
2020-08-05 22:12           ` Konrad Dybcio
2020-08-05 22:12             ` Konrad Dybcio
2020-08-05 19:32     ` Pavel Machek
2020-08-05 19:32       ` Pavel Machek

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=CACRpkdY+qb-d31cZjWtscSOMLxdvyaHc5xFbTd-k8AA0_fTXUg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=torvalds@linux-foundation.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 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.