On Thu, 22 Dec 2005, Randy.Dunlap wrote:
>
> Andrew can surely answer that, but it could be something as
> simple as wanting to build a more stable kernel (one without
> so much churn), so that things have time to mature and
> improve without breaking so many other things...
Not to mention that when this gets into the kernel, Andrew's the one that
will have to deal with a ton of "switch semaphores to mutexes" patches
that will slowly update the entire kernel. These patches will probably
continue to come in for a few years. ;)
IIRC, that was one of his rational reasons why he didn't want the timer
name change.
-- Steve
-
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 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
- Re: [patch 0/9] mutex subsystem, -V4
[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]