Messages in this thread | | | Subject | Re: Linux 2.6.21-rc1 | From | Daniel Walker <> | Date | Wed, 21 Feb 2007 12:49:33 -0800 |
| |
On Wed, 2007-02-21 at 21:43 +0100, Thomas Gleixner wrote: > On Wed, 2007-02-21 at 12:00 -0800, Daniel Walker wrote: > > There's a compile failure during my bisect. > > > > distcc[3863] ERROR: compile /tmp//hrtimer.tmp.dwalker1.3795.i on dwalker3/120 failed > > kernel/hrtimer.c: In function 'hrtimer_cpu_notify': > > kernel/hrtimer.c:884: warning: implicit declaration of function 'clockevents_notify' > > kernel/hrtimer.c:884: error: 'CLOCK_EVT_NOTIFY_CPU_DEAD' undeclared (first use in this function) > > kernel/hrtimer.c:884: error: (Each undeclared identifier is reported only once > > kernel/hrtimer.c:884: error: for each function it appears in.) > > drivers/ide/setup-pci.c: In function 'ide_scan_pcibus': > > drivers/ide/setup-pci.c:866: warning: ignoring return value of '__pci_register_driver', declared with attribute warn_unused_result > > make[1]: *** [kernel/hrtimer.o] Error 1 > > hrmpf. we made it bisectable at some point.
It was related some code under a hot plug ifdef ..
Here's the final commit from the bisect which caused it . It says "No changes to existing functionality" ?
e9e2cdb412412326c4827fc78ba27f410d837e6e is first bad commit commit e9e2cdb412412326c4827fc78ba27f410d837e6e Author: Thomas Gleixner <tglx@linutronix.de> Date: Fri Feb 16 01:28:04 2007 -0800
[PATCH] clockevents: i386 drivers
Add clockevent drivers for i386: lapic (local) and PIT/HPET (global). Update the timer IRQ to call into the PIT/HPET driver's event handler and the lapic-timer IRQ to call into the lapic clockevent driver. The assignement of timer functionality is delegated to the core framework code and replaces the compile and runtime evalution in do_timer_interrupt_hook()
Use the clockevents broadcast support and implement the lapic_broadcast function for ACPI.
No changes to existing functionality.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |