linux-kernel - Re: linux-next: build failure after merge of the pci tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Jan 2011 20:48:21 +0530
From:	<Narendra_K@...l.com>
To:	<sfr@...b.auug.org.au>
CC:	<jbarnes@...tuousgeek.org>, <linux-next@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <Narendra_K@...l.com>,
	<Jordan_Hargrave@...l.com>, <Matt_Domsch@...l.com>
Subject: Re: linux-next: build failure after merge of the pci tree

On Mon, Jan 10, 2011 at 07:24:11AM +0530, Stephen Rothwell wrote:
> Hi Jesse,
> 
> After merging the pci tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/built-in.o: In function `T.647':
> pci-label.c:(.text+0x28514): undefined reference to `utf16s_to_utf8s'
> 
> Caused by commit a6247cd4be20cb5439db5cb7b0b6cc67fdc8e2a2 ("PCI: export
> ACPI _DSM provided firmware instance number and string to sysfs").
> 
> I have used the pci tree from next-20110107 for today.

[ It looks like my earlier post did not hit the lists, so reposting ]

Hi, 

I did a git pull of linux-next-20110110 (topmost commit is 
4c897f27ad2668534f719202a3b88abe8ec31011) and applied the patch. With 
CONFIG_DMI and CONFIG_ACPI both set, I did not encounter this build failure. 
The definition for `utf16s_to_utf8s' is available in 'include/linux/nls.h' 
which is included in 'drivers/pci/pci-label.c' and the build succeeded. Sorry 
if I am missing something here.

Stephen,

Could you share the .config which caused this build failure ?

With regards,
Narendra K


--
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/