From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: build failure after merge of the final tree (pci tree related)
Date: Wed, 7 Dec 2011 09:13:54 -0800 [thread overview]
Message-ID: <20111207091354.412a9102@jbarnes-desktop> (raw)
In-Reply-To: <CAErSpo5fO87Aj8_PcdTT5V1JC6D8_o5WEpEMmHCeC=2PA9rkoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
On Wed, 7 Dec 2011 08:25:39 -0700
Bjorn Helgaas <bhelgaas@google.com> wrote:
> On Wed, Dec 7, 2011 at 8:08 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> > On Tue, Dec 6, 2011 at 11:05 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >> Hi all,
> >>
> >> After merging the final tree, today's linux-next build (sparc64 defconfig)
> >> failed like this:
> >>
> >> arch/sparc/kernel/pci.c: In function 'pci_scan_one_pbm':
> >> arch/sparc/kernel/pci.c:697:7: error: incompatible type for argument 5 of 'pci_create_root_bus'
> >> include/linux/pci.h:665:17: note: expected 'struct list_head *' but argument is of type 'struct list_head'
> >>
> >> Caused by commit fa3cec8aff53 ("sparc/PCI: convert to pci_create_root_bus
> >> ()"). Same typo as for the powerpc tree. :-( Please double check the
> >> rest of those changes, please.
> >>
> >> I applied the following patch for today.
> >
> > Thanks for doing that, sorry for the trouble. I don't have a set of
> > cross-compilers, unfortunately, but I will inspect the rest manually.
> > Do we have to discover problems one-by-one, or can you tell us about
> > any other arch build problems at the same time?
>
> I checked the rest manually and didn't find any similar problems.
>
> The corrected patch attached (same as with Stephen's fixup) is
> attached. Also available
> at git://github.com/bjorn-helgaas/linux.git on the "pci-scan-v5"
> branch as c0cab2621d0cf75e86fbbad44d0b2b84c3a42f97)
Squashed the fix into the original patch. Thanks guys.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-07 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 6:05 linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell
2011-12-07 15:08 ` Bjorn Helgaas
2011-12-07 15:25 ` Bjorn Helgaas
2011-12-07 17:13 ` Jesse Barnes [this message]
2011-12-07 20:24 ` Stephen Rothwell
2011-12-08 19:01 ` Tony Luck
2011-12-09 3:53 ` Bjorn Helgaas
2011-12-09 20:02 ` Luck, Tony
2011-12-12 20:53 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2012-06-12 4:54 Stephen Rothwell
2012-06-12 15:31 ` Bjorn Helgaas
2012-06-13 0:50 ` Stephen Rothwell
2012-06-13 23:20 ` Bjorn Helgaas
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=20111207091354.412a9102@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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