linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Rob Herring <robh@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-brgl tree
Date: Tue, 23 Nov 2021 13:04:18 +1100	[thread overview]
Message-ID: <20211123130418.17878c41@canb.auug.org.au> (raw)
In-Reply-To: <20211118112951.2b788952@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

Hi all,

On Thu, 18 Nov 2021 11:29:51 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Tue, 16 Nov 2021 10:51:12 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the gpio-brgl tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/gpio/gpio-xlp.c:300:16: error: 'GPIO_VARIANT_VULCAN' undeclared here (not in a function)
> >   300 |  { "BRCM9006", GPIO_VARIANT_VULCAN },
> >       |                ^~~~~~~~~~~~~~~~~~~
> > 
> > Caused by commit
> > 
> >   ea708ac5bf41 ("gpio: xlp: Remove Netlogic XLP variants")
> > 
> > I have used the gpio-bgrl tree from next-20211115 for today.  
> 
> I am still getting this failure :-(

And still :-( :-(

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-11-23  2:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 23:51 linux-next: build failure after merge of the gpio-brgl tree Stephen Rothwell
2021-11-17 21:29 ` Rob Herring
2021-11-18  0:29 ` Stephen Rothwell
2021-11-23  2:04   ` Stephen Rothwell [this message]
2021-12-02  3:16     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  3:33 Stephen Rothwell
2024-02-23  7:51 ` Bartosz Golaszewski
2024-02-23 12:29   ` Andy Shevchenko
2024-02-25  1:58   ` Stephen Rothwell
2024-02-26 19:07     ` Bartosz Golaszewski
2023-10-13  4:14 Stephen Rothwell
2023-10-13  6:44 ` Bartosz Golaszewski
2023-03-23  1:29 Stephen Rothwell
2023-03-22 19:50 ` William Breathitt Gray
2023-03-23 13:32   ` Bartosz Golaszewski
2021-12-20  5:51 Stephen Rothwell
2021-12-20 12:46 ` Andy Shevchenko
2021-12-13 20:31 broonie
2021-12-14  3:12 ` Florian Fainelli
2021-12-17  6:17   ` Stephen Rothwell
2021-12-17  9:14     ` Bartosz Golaszewski
2021-02-18  6:54 Stephen Rothwell

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=20211123130418.17878c41@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brgl@bgdev.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@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).