linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jon Mason <mason@myri.com>,
	Jordan Hargrave <jordan_hargrave@dell.com>
Subject: Re: linux-next: build failure after merge of the pci-current tree
Date: Tue, 2 Aug 2011 08:53:27 -0700	[thread overview]
Message-ID: <20110802085327.61325b3c@jbarnes-desktop> (raw)
In-Reply-To: <20110802112336.fd2d2b577a2a71892189733b@canb.auug.org.au>

On Tue, 2 Aug 2011 11:23:36 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Jesse,
> 
> On Tue, 2 Aug 2011 10:48:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the pci-current tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > ERROR: ".pcie_bus_configure_settings" [drivers/pci/hotplug/pci_hotplug.ko] undefined!
> > 
> > Caused by commit b03e7495a862 ("PCI: Set PCI-E Max Payload Size on
> > fabric").  Missing EXPORT_SYMBOL?
> > 
> > I have used the pci-current tree from next-20110801 for today.
> 
> And the same for the pci tree (which is identical today).

Jon just sent me the fix and I pushed it out.  Should be fixed now.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  parent reply	other threads:[~2011-08-02 15:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  0:48 linux-next: build failure after merge of the pci-current tree Stephen Rothwell
2011-08-02  1:23 ` Stephen Rothwell
2011-08-02  5:01   ` [PATCH] PCI: export pcie_bus_configure_settings symbol Jon Mason
2011-08-02 15:53   ` Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05  0:07 linux-next: build failure after merge of the pci-current tree 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
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
2011-07-07  0:58 Stephen Rothwell
2011-07-07 15:52 ` Jesse Barnes
2011-07-07 18:19   ` Ram Pai
2011-07-08 22:49     ` Jesse Barnes

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=20110802085327.61325b3c@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=jordan_hargrave@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mason@myri.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;
as well as URLs for NNTP newsgroup(s).