From: Randy Dunlap <rdunlap@xenotime.net>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 9 (ibmphp)
Date: Fri, 16 Dec 2011 10:42:13 -0800 [thread overview]
Message-ID: <4EEB9105.3030100@xenotime.net> (raw)
In-Reply-To: <CAErSpo5dbAJiJ4FhR4bso+4MnJ9mk45T2Z+spmdzRr95w8jAZg@mail.gmail.com>
On 12/13/2011 04:41 PM, Bjorn Helgaas wrote:
> On Mon, Dec 12, 2011 at 10:20 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>> On 12/09/2011 10:51 AM, Randy Dunlap wrote:
>>>
>>> On Thu, December 8, 2011 9:32 pm, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20111208:
>>>
>>> (This build error was first seen in 20111208.)
>>>
>>>
>>> ERROR: "pci_scan_bus" [drivers/pci/hotplug/ibmphp.ko] undefined!
>>>
>>> Full randconfig file is attached.
>>
>>
>> Same for 20111212.
>
> I changed pci_scan_bus() from an inline function (visible to modules)
> to a normal function (by default, not visible to modules), which broke
> the ibmphp.ko build.
>
> The updated patch is attached, as well as the incremental change (just
> adding "EXPORT_SYMBOL(pci_scan_bus);".
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
(although those git sha hashes in the filenames did confuse 'patch';
maybe I need a newer version of patch)
> (Also available at git://github.com/bjorn-helgaas/linux.git on the "pci-scan-v6"
> branch as bef4a9eefaa69dd9bc998e29d619127d1653683d)
>
> Bjorn
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-12-16 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111209163247.1de15dcb5b735ca5e1ad030b@canb.auug.org.au>
2011-12-09 18:51 ` linux-next: Tree for Dec 9 (ibmphp) Randy Dunlap
2011-12-12 17:20 ` Randy Dunlap
2011-12-14 0:41 ` Bjorn Helgaas
2011-12-14 16:30 ` Jesse Barnes
2011-12-16 18:42 ` Randy Dunlap [this message]
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=4EEB9105.3030100@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).