Re: [PATCH 3/5] i386: hpet assumes boot cpu is 0

On Tue, 2007-05-08 at 02:44 -0700, Chris Wright wrote:
> I fixed this in x86_64.  Looks like the kind of thing that will break
> voyager on i386.

voyager has hpet ? Anyway good point.

	tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] x86-64 highres/dyntick support
  - From: Thomas Gleixner <[email protected]>
- Re: [PATCH] x86-64 highres/dyntick support
  - From: Chris Wright <[email protected]>
- Re: [PATCH] x86-64 highres/dyntick support
  - From: Thomas Gleixner <[email protected]>
- Re: [PATCH] x86-64 highres/dyntick support
  - From: Chris Wright <[email protected]>
- [PATCH 3/5] i386: hpet assumes boot cpu is 0
  - From: Chris Wright <[email protected]>

Prev by Date: [PATCH 1/3] [POWERPC] 8xx: mpc885ads pcmcia support
Next by Date: [PATCH 4/5] i386: i8253 clockevent shutdown and unused using pit
Previous by thread: [PATCH 3/5] i386: hpet assumes boot cpu is 0
Next by thread: [PATCH 5/5] x86_64: restore restore nohpet cmdline
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]