linux-kernel - Re: linux-next: Tree for October 25 (acpi/apei-related)

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

Date:	Mon, 25 Oct 2010 16:51:45 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-acpi@...r.kernel.org
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for October 25 (acpi/apei-related)

On Mon, 25 Oct 2010 14:58:34 +1100 Stephen Rothwell wrote:

> Hi all,

drivers/built-in.o: In function `herr_record_init':
(.text+0x85149): undefined reference to `trace_clock_local'
drivers/built-in.o: In function `herr_record_alloc':
(.text+0x851ab): undefined reference to `trace_clock_local'
drivers/built-in.o: In function `herr_record_alloc':
(.text+0x8521c): undefined reference to `trace_clock_local'


config ACPI_APEI
	bool "ACPI Platform Error Interface (APEI)"
	depends on X86
	select HERR_DEV_CORE

but kernel/trace/trace_clock is not built unless one of these symbols
is enabled:

obj-$(CONFIG_FUNCTION_TRACER) += trace/
obj-$(CONFIG_TRACING) += trace/
obj-$(CONFIG_X86_DS) += trace/
obj-$(CONFIG_RING_BUFFER) += trace/

and in this case, none of these is enabled.

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