On Sep 10 2007 10:22, Andrew Morton wrote: >> Unless folks have strong objection to it, I prefer "cptctlr", the way it is. > >Kernel code is write-rarely, read-often. I think you mean __read_mostly. :-) Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] Hookup group-scheduler with task container infrastructure
- From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
- Re: [PATCH] Hookup group-scheduler with task container infrastructure
- From: Jan Engelhardt <jengelh@computergmbh.de>
- Re: [PATCH] Hookup group-scheduler with task container infrastructure
- From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
- Re: [PATCH] Hookup group-scheduler with task container infrastructure
- From: Andrew Morton <akpm@linux-foundation.org>
- [PATCH] Hookup group-scheduler with task container infrastructure
- Prev by Date: Re: [PATCH] list.h: add list_for_each_entry_continue_rcu
- Next by Date: Re: [PATCH] Hookup group-scheduler with task container infrastructure
- Previous by thread: Re: [PATCH] Hookup group-scheduler with task container infrastructure
- Next by thread: Re: [Devel] Re: [PATCH] Hookup group-scheduler with task container infrastructure
- Index(es):
 |