> ... > in x86_64/Kconfig has EARLY_PRINTK too > > config EARLY_PRINTK > bool > default y I noticed this too. So on x86_64 it was unconditionally enabled whereas with i386 (and the merged files) if it an option that can be turned off. Randy - did you realise this when you did the merge? Sam - 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: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- From: Randy Dunlap <[email protected]>
- Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- References:
- Linux v2.6.24-rc1
- From: Linus Torvalds <[email protected]>
- Re: Linux v2.6.24-rc1
- From: Christoph Hellwig <[email protected]>
- Re: Linux v2.6.24-rc1
- From: Sam Ravnborg <[email protected]>
- Re: Linux v2.6.24-rc1
- From: Ingo Molnar <[email protected]>
- [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- From: Sam Ravnborg <[email protected]>
- Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- From: Randy Dunlap <[email protected]>
- Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- From: "Yinghai Lu" <[email protected]>
- Linux v2.6.24-rc1
- Prev by Date: Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- Next by Date: Re: [PATCH] Permit silencing of __deprecated warnings.
- Previous by thread: Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- Next by thread: Re: [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs
- Index(es):
 |