Re: [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup

> It was suggested to me in an earlier patch set to move RESERVE_HOTADD to
> Kconfig. 

It doesn't make any sense to me.

> I can make it a non-user option.  It seems that MEMORY_HOTPLUG 
> is a user options so I figured why not make RESERVE one as well.  Also I
> don't think people should use reserve with sparsmem. 

There should be a single high level Kconfig option for each feature.


-Andi
-
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:
- [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup
  - From: keith mannthey <[email protected]>
- Re: [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup
  - From: Andi Kleen <[email protected]>
- Re: [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup
  - From: keith mannthey <[email protected]>

Prev by Date: Re: via sata oops on init
Next by Date: Re: Building the kernel on an SMP box?
Previous by thread: Re: [Patch] 1/5 in support of hot-add memory x86_64 nodes_add cleanup
Next by thread: [Patch] 2/5 in support of hot-add memory x86_64 create arch_find_node
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]