Re: [PATCH] get rid if __cpuinit and __cpuexit
- From: "Tony Luck" <tony.luck@xxxxxxxxx>
- Date: Wed, 22 Oct 2008 17:12:14 -0700
On Wed, Oct 22, 2008 at 3:30 PM, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
as discussed briefly at the kernel summit; __cpuinit and __cpuexit are
causing a ton more complexity than they're worth (just see how many
section warnings an average build has);
Nice idea ... but on ia64 I actually see *more* section mismatch
warnings with this patch applied :-(
generic_defconfig goes up from 6 to 7
tiger_defconfig rises from 3 to 6
-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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] get rid if __cpuinit and __cpuexit
- From: Arjan van de Ven
- Re: [PATCH] get rid if __cpuinit and __cpuexit
- References:
- [PATCH] get rid if __cpuinit and __cpuexit
- From: Arjan van de Ven
- [PATCH] get rid if __cpuinit and __cpuexit
- Prev by Date: [PATCH] mmc: trivial annotation of 'blocks'
- Next by Date: [git pull] PCI pull request #2 for 2.6.28
- Previous by thread: [PATCH] get rid if __cpuinit and __cpuexit
- Next by thread: Re: [PATCH] get rid if __cpuinit and __cpuexit
- Index(es):
Relevant Pages
|
