On Fri, 30 Nov 2007, Ingo Molnar wrote: > if you treat testing and review efforts like that they might have to > wait even longer :-( "My stuff is there somewhere amongst 1415 -mm > patches. Thank you for your interest and buzz off already." Well I guess you have to get used to maintainership I think. F.e. the s390 people tested this patchset without requiring a backport. Typically arch maintainers test mm and do not force the patches back into mainline. I am a bit surprised since Andi and I never had this issue. - 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:
- References:
- [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Christoph Lameter <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Ingo Molnar <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Ingo Molnar <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Christoph Lameter <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Ingo Molnar <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Christoph Lameter <[email protected]>
- Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- From: Ingo Molnar <[email protected]>
- [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- Prev by Date: Re: Possibly SATA related freeze killed networking and RAID
- Next by Date: Re: [BUG] Strange 1-second pauses during Resume-from-RAM
- Previous by thread: Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- Next by thread: Re: [patch 0/3] Per cpu relocation to ZERO and x86_32 percpu ops on x86_64
- Index(es):
 |