RE: "double" hpet clocksource && hard freeze [bisected]

> I have a double "hpet" entry in "available_clocksource":
>	$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
>	tsc hpet hpet acpi_pm jiffies

Oops.  If seems that both drivers/char/hpet.c and arch/x86_64/kernel/hpet.c
both register a clocksource named "hpet".  Probably a result of bringing
back to life a long lost patch, and having someone else (John Stultz, according
to git blame) make a similar change to a different file in the intervening
time.

Presumably the thing to do would be merge the x86_64 specific version
into the drivers/char/hpet.c version?

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

---

• Follow-Ups:
  • RE: "double" hpet clocksource && hard freeze [bisected]
    • From: john stultz <[email protected]>

• References:
  • "double" hpet clocksource && hard freeze [bisected]
    • From: Paolo Ornati <[email protected]>

• Prev by Date: RE: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
• Next by Date: Re: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
• Previous by thread: Re: "double" hpet clocksource && hard freeze [bisected]
• Next by thread: RE: "double" hpet clocksource && hard freeze [bisected]
• 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]