linux-kernel - Re: linux-next: Tree for Nov 9 (build errors summary)

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-prev] [day] [month] [year] [list]

Date:	Wed, 09 Nov 2011 12:55:24 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	x86 maintainers <x86@...nel.org>, Greg KH <gregkh@...e.de>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: Re: linux-next: Tree for Nov 9 (build errors summary)

On 11/09/2011 12:11 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 09, 2011 at 11:23:21AM -0800, Randy Dunlap wrote:
>> On 11/08/2011 06:58 PM, Stephen Rothwell wrote:
>>> Hi all,
>>
>>
>> 1.  on i386, when CONFIG_SMP is not enabled:
>>
>> arch/x86/built-in.o: In function `hpet_setup_msi_irq':
>> hpet.c:(.text+0x12114): undefined reference to `arch_setup_hpet_msi'
>> hpet.c:(.text+0x12123): undefined reference to `destroy_irq'
>> arch/x86/built-in.o: In function `hpet_msi_capability_lookup':
>> hpet.c:(.text+0x121fb): undefined reference to `create_irq_nr'
>> arch/x86/built-in.o:(.data+0x314): undefined reference to `native_setup_msi_irqs'
>> arch/x86/built-in.o:(.data+0x318): undefined reference to `native_teardown_msi_irq'
> 
> This looks new. When did it start happening? err, Any idea which patch
> might have caused this?

I first reported it on the Nov. 7 linux-next tree.

No idea what patch might be causing it, sorry.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/