Martin J. Bligh wrote:
>
> --Andi Kleen <[email protected]> wrote (on Monday, October 31, 2005 03:12:17 +0100):
>
>
>>On Monday 31 October 2005 01:17, Bob Picco wrote:
>>Ok the question is - why did nobody submit this patch in time? When
>>sparse was merged I assumed folks would actually test and maintain
>>it. But that doesn't seem to be the case? Somewhat surprising.
We are activly maintaining sparsemem. But we do seem to have fallen
short on the testing front on some of the architectures. I'm looking
right now into getting some automated testing sorted out for SPARSEMEM
specifically so that we catch this stuff much earlier in the pipeline,
as its much simpler for us to find the earlier a problem appears.
>>I personally don't care much about sparsemem right now because it doesn't have
>>any advantage and if it's unmaintained would consider to mark it
>>CONFIG_BROKEN. That's simply because we can't have highly experimental
>>CONFIGs in a production kernel that unsuspecting users can just set and break
>>their configuration.
>>
>>Dave, is there someone in charge for sparsemem on x86-64?
I had assumed that it was being maintained, but its not obvious from
this thread that we're all on the same page. But we'll find out and get
that sorted.
-apw
-
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]
