[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ED3036A092A28F4C91B0B4360DD128EA3032134C@shzsmsx502.ccr.corp.intel.com>
Date: Fri, 18 Dec 2009 16:57:55 +0800
From: "Cui, Dexuan" <dexuan.cui@...el.com>
To: Jesse Barnes <jbarnes@...tuousgeek.org>,
Randy Dunlap <randy.dunlap@...cle.com>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: Tree for December 17 (pci/quirks)
Jesse Barnes wrote:
> On Thu, 17 Dec 2009 09:55:06 -0800
> Randy Dunlap <randy.dunlap@...cle.com> wrote:
>
>> On Thu, 17 Dec 2009 16:58:40 +1100 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> My usual call for calm: please do not put stuff destined for 2.6.34
>>> into linux-next trees until after 2.6.33-rc1.
>>>
>>> Changes since 20091216:
>>
>>
>> When CONFIG_PCI_QUIRKS=n:
>>
>> drivers/built-in.o: In function `pci_dev_reset':
>> pci.c:(.text+0xdb0b): undefined reference to `pci_dev_reset_methods'
>> pci.c:(.text+0xdb2b): undefined reference to `pci_dev_reset_methods'
>> pci.c:(.text+0xdb85): undefined reference to `pci_dev_reset_methods'
>>
>>
>> pci_dev_reset() calls (inlined) pci_dev_specific_reset(),
>> which references pci_dev_reset_methods, which does not exist.
>
> Dexuan, can you fix this up?
Hi Jesse,
I have posted a small patch in linux-pci ML just now.
I can reproduce the build failure and with the patch I posted I can verify the build can pass successfully.
Please have a look.
Thanks,
-- Dexuan--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists