Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init

On Tue, 10 Jul 2007, Adrian Bunk wrote:

> But I'm not convinced it's really worth manually forcing noinline only 
> for moving a few bytes to __init in the CONFIG_NUMA=y case - in the  
> long term this will only bit rot.

Allright then

Acked-by: Christoph Lameter <[email protected]>

-
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/

---

• References:
  • [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
    • From: Adrian Bunk <[email protected]>
  • Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
    • From: Christoph Lameter <[email protected]>
  • Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Re: [PATCH] fix sparse problems with ARRAY_SIZE
• Next by Date: Re: [PATCH] include private data mappings in RLIMIT_DATA limit
• Previous by thread: Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
• Next by thread: [2.6 patch] rrunner.c:rr_init() must be __devinit
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]