On 05/29/2017 01:41 PM, Michal Hocko wrote: > From: Michal Hocko <[email protected]> > > 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated > node") has introduced CONFIG_MOVABLE_NODE without a good explanation on > why it is actually useful. It makes a lot of sense to make movable node > semantic opt in but we already have that because the feature has to be > explicitly enabled on the kernel command line. A config option on top > only makes the configuration space larger without a good reason. It also > adds an additional ifdefery that pollutes the code. Just drop the config > option and make it de-facto always enabled. This shouldn't introduce any > change to the semantic. > > Acked-by: Reza Arbab <[email protected]> > Signed-off-by: Michal Hocko <[email protected]>
Acked-by: Vlastimil Babka <[email protected]>
