From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the pci-current tree
Date: Fri, 8 Jul 2011 15:49:57 -0700 [thread overview]
Message-ID: <20110708154957.253b26b2@jbarnes-desktop> (raw)
In-Reply-To: <20110707181910.GD3543@ram-ThinkPad-T61>
On Thu, 7 Jul 2011 11:19:10 -0700
Ram Pai <linuxram@us.ibm.com> wrote:
> On Thu, Jul 07, 2011 at 08:52:05AM -0700, Jesse Barnes wrote:
> > On Thu, 7 Jul 2011 10:58:23 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > Hi Jesse,
> > >
> > > After merging the pci-current tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like this:
> > >
> > > drivers/built-in.o:(.toc1+0xb98): undefined reference to `pci_realloc'
> > >
> > > Caused by commit 72007d2b4797 ("PCI: conditional resource-reallocation
> > > through kernel parameter pci=realloc").
> > >
> > > I have used the pci-current tree from next-20110706 for today.
> >
> > Oops, x86 bits used in common code. I've pushed a fix that just moves
> > the variable into setup-bus.c rather than x86/pci/common.c.
>
> Jesse,
>
> I have fixed the problem and have a better patch. See if it is acceptable for you.
Yes, much better, thanks. I'll send it to Linus tomorrow if I don't
hear any complaints.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-08 22:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 0:58 linux-next: build failure after merge of the pci-current tree Stephen Rothwell
2011-07-07 15:52 ` Jesse Barnes
2011-07-07 18:19 ` Ram Pai
2011-07-08 22:49 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-02 0:48 Stephen Rothwell
2011-08-02 1:23 ` Stephen Rothwell
2011-08-02 15:53 ` Jesse Barnes
2011-11-03 1:53 Stephen Rothwell
2011-11-03 2:04 ` Jesse Barnes
2011-11-03 2:37 ` Stephen Rothwell
2011-11-03 3:22 ` Stephen Rothwell
2011-11-03 3:32 ` Stephen Rothwell
2011-11-03 5:19 ` Stephen Rothwell
2011-11-03 15:02 ` Jesse Barnes
2012-01-05 0:07 Stephen Rothwell
2012-01-05 0:11 ` Jesse Barnes
2012-01-05 0:19 ` Stephen Rothwell
2012-01-05 0:27 ` Dave Jones
2012-01-05 2:16 ` 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=20110708154957.253b26b2@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--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