This patch seems to have a rather low value-to-noise ratio. Why on earth do we want to do this? - 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:
- [RFC] Splitting out kernel<=>userspace ABI headers
- From: Kyle Moffett <[email protected]>
- Re: [RFC] Splitting out kernel<=>userspace ABI headers
- From: [email protected] (H. Peter Anvin)
- Re: [RFC] Splitting out kernel<=>userspace ABI headers
- From: Kyle Moffett <[email protected]>
- [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
- From: Kyle Moffett <[email protected]>
- Re: [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
- From: Kyle Moffett <[email protected]>
- [RFC] Splitting out kernel<=>userspace ABI headers
- Prev by Date: Re: [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
- Next by Date: Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- Previous by thread: Re: [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
- Next by thread: Re: [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
- Index(es):
