Christoph wrote: > I wish I knew how we can improve the communication. I have discussed this > for two months now and tried to respond to every objection and concern > that came up. The success of communication must be measured by what is heard, not what is said. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <[email protected]> 1.925.600.0401 - 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:
- NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Andi Kleen <[email protected]>
- Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Andi Kleen <[email protected]>
- Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Christoph Lameter <[email protected]>
- Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Andi Kleen <[email protected]>
- Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Andrew Morton <[email protected]>
- Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- From: Christoph Lameter <[email protected]>
- NUMA mempolicy /proc code in mainline shouldn't have been merged
- Prev by Date: Re: [PATCH] reduce sizeof(struct file)
- Next by Date: Re: Supporting ACPI drive hotswap
- Previous by thread: Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- Next by thread: Re: Fw: Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
- Index(es):