Arjan van de Ven wrote:
Also why should we care so much for multi directory modules?I suspect Jeff didn't mean it like that, but instead assumed that multi-directory would be harder so that starting with single-directory would be a good start...
Correct... Jeff - 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:
- Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- From: Sam Ravnborg <[email protected]>
- Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- References:
- [patch 1/7] Make __always_inline actually force always inlining
- From: Arjan van de Ven <[email protected]>
- [patch 2/7] enable unit-at-a-time optimisations for gcc4
- From: Arjan van de Ven <[email protected]>
- Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- From: Jeff Garzik <[email protected]>
- Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- From: Sam Ravnborg <[email protected]>
- Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- From: Arjan van de Ven <[email protected]>
- [patch 1/7] Make __always_inline actually force always inlining
- Prev by Date: Re: [PATCH] bio: gcc warning fix.
- Next by Date: 2.6.15 - possible serial port problem?
- Previous by thread: Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- Next by thread: Re: [patch 2/7] enable unit-at-a-time optimisations for gcc4
- Index(es):
 |