Andi Kleen <[email protected]> wrote:
>
>
> > Anyway. From the implementation I can see what the code is doing. But I
> > see no description of what it is _supposed_ to be doing. (The process of
> > finding differences between these two things is known as "debugging"). I
> > could kludge things by setting MAX_ACTIVE_REGIONS to 1000000, but enough.
> > I look forward to the next version ;)
>
> Or we could just keep the working old code.
>
> Can somebody remind me what this patch kit was supposed to fix or improve again?
>
Well, it creates arch-neutral common code, teaches various architectures
use it. It's the sort of thing we do all the time.
These things are opportunities to eliminate crufty arch code which few
people understand and replace them with new, clean common code which lots
of people understand. That's not a bad thing to be doing.
-
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/
[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]
