Re: [patch] sched_clock(): cleanups, #2

> I wonder if this was the source of the lockdep selftest failures, or the
> mystery hang this patch caused (IIRC)..

No, the inbalance was just on the ftp server for an hour or so.
I doubt anybody except Ingo ever saw that code.

I introduced it while changing the callbacks around to make the code
easier to read.

-Andi
-
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:
  • Re: [patch] x86_64: fix sched_clock()
    • From: Andi Kleen <[email protected]>
  • Re: [patch] x86_64: fix sched_clock()
    • From: Ingo Molnar <[email protected]>
  • Re: [patch] x86_64: fix sched_clock()
    • From: Andi Kleen <[email protected]>
  • Re: [patch] x86_64: fix sched_clock()
    • From: Ingo Molnar <[email protected]>
  • [patch] sched_clock(): cleanups, #2
    • From: Ingo Molnar <[email protected]>
  • Re: [patch] sched_clock(): cleanups, #2
    • From: Andi Kleen <[email protected]>
  • Re: [patch] sched_clock(): cleanups, #2
    • From: Ingo Molnar <[email protected]>
  • Re: [patch] sched_clock(): cleanups, #2
    • From: Andi Kleen <[email protected]>
  • Re: [patch] sched_clock(): cleanups, #2
    • From: Andrew Morton <[email protected]>
  • Re: [patch] sched_clock(): cleanups, #2
    • From: Daniel Walker <[email protected]>

• Prev by Date: Re: [patch] sched_clock(): cleanups, #2
• Next by Date: Re: [2/3] 2.6.22-rc2: known regressions v2
• Previous by thread: Re: [patch] sched_clock(): cleanups, #2
• Next by thread: Re: [patch] sched_clock(): cleanups, #2
• 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]