mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Logan Odell <loganodell@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in the final build
Date: Tue, 29 Sep 2026 11:07:12 -0500	[thread overview]
Message-ID: <20260929160712.GA2327182@bhelgaas> (raw)
In-Reply-To: <6c7088c6-28dd-4e5b-bcb0-0d951183b884@sirena.org.uk>

On Mon, Sep 28, 2026 at 03:13:13PM +0100, Mark Brown wrote:
> On Fri, Sep 25, 2026 at 05:09:53PM +0100, Mark Brown wrote:
> > Hi all,
> > 
> > In the final build today's linux-next build (i386 defconfig) failed like
> > this:
> > 
> > /tmp/next/build/drivers/pci/probe.c: In function 'pci_class':
> > /tmp/next/build/drivers/pci/probe.c:1902:12: error: unused variable 'rev' [-Werror=unused-variable]
> >  1902 |         u8 rev;
> >       |            ^~~
> > 
> > Caused by commit
> > 
> >    8a2a9fa37b814 (PCI/IOV: Read VF config values that need not match PF)
> > 
> > I have reverted that commit for today.
> 
> This issue is still present today.

Sorry, it should be fixed in the current pci/next
(81bebadfa0f7 ("Merge branch 'pci/misc'"))

  reply	other threads:[~2026-09-29 16:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 16:09 Mark Brown
2026-09-28 14:13 ` Mark Brown
2026-09-29 16:07   ` Bjorn Helgaas [this message]
2026-09-29 21:18     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-08-18 20:54 Mark Brown
2026-08-18 23:49 ` Josh Poimboeuf
2026-08-19  8:09   ` Ard Biesheuvel
2026-07-13 17:48 Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47   ` Manuel Ebner
2026-07-17 14:35     ` Greg Kroah-Hartman
2026-07-17 14:40       ` Johan Hovold
2026-07-17 14:54         ` Mark Brown
2026-07-17 15:06           ` Johan Hovold
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-06 14:50 linux-next: build " Mark Brown
2026-07-06 14:52 ` Johannes Berg
2026-06-10 15:51 Mark Brown
2026-01-21 17:14 Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24   ` Mark Brown
2026-01-21 18:14     ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24   ` Miguel Ojeda
2026-01-22 11:20     ` Mark Brown
2026-01-22  0:42   ` Deborah Brouwer
2026-01-22 11:17   ` Mark Brown

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=20260929160712.GA2327182@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=loganodell@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®