Re: [PATCH 1/5] x86: make platform/intel-quark/imr.c explicitly non-modular

2016-02-15 Thread Bryan O'Donoghue
On Sun, 2016-02-14 at 18:09 -0500, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/platform/x86/Kconfig:config INTEL_IMR > drivers/platform/x86/Kconfig: bool "Intel Isolated Memory Region > support" > > ...meaning that it currently is not

Re: [PATCH 1/5] x86: make platform/intel-quark/imr.c explicitly non-modular

2016-02-15 Thread Bryan O'Donoghue
On Sun, 2016-02-14 at 18:09 -0500, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/platform/x86/Kconfig:config INTEL_IMR > drivers/platform/x86/Kconfig: bool "Intel Isolated Memory Region > support" > > ...meaning that it currently is not

[PATCH 1/5] x86: make platform/intel-quark/imr.c explicitly non-modular

2016-02-14 Thread Paul Gortmaker
The Kconfig currently controlling compilation of this code is: drivers/platform/x86/Kconfig:config INTEL_IMR drivers/platform/x86/Kconfig: bool "Intel Isolated Memory Region support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 1/5] x86: make platform/intel-quark/imr.c explicitly non-modular

2016-02-14 Thread Paul Gortmaker
The Kconfig currently controlling compilation of this code is: drivers/platform/x86/Kconfig:config INTEL_IMR drivers/platform/x86/Kconfig: bool "Intel Isolated Memory Region support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is