linux-kernel - Re: linux-next: build failure after merge of the tip 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-prev] [day] [month] [year] [list]

Date:	Tue, 28 Jun 2011 12:55:38 +0200
From:	Stijn Devriendt <highguy@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the tip tree

I've already reported this to Thomas with a patch attached.

See https://lkml.org/lkml/2011/6/25/62

Regards,
Stijn

On Mon, Jun 27, 2011 at 6:22 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/kernel/i8253.c: In function 'setup_pit_timer':
> arch/x86/kernel/i8253.c:22:2: error: implicit declaration of function 'clockevent_i8253_init'
> arch/x86/kernel/i8253.c:23:24: error: 'i8253_clockevent' undeclared (first use in this function)
>
> Caused by commit 2739ce151665 ("x86: Use common i8253 clockevent").
> clockevent_i8253_init() doesn't appear to be declared in any header file
> even though it is introduced as a global function in commit 9f9119424bbc
> ("i8253: Create common clockevent implementation").  Similarly for
> i8253_clockevent.
>
> I have used the tip tree from next-20110624 for today.
> --
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
--
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/