Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular

Hi Paul, On Mon, 28 Sep 2015, Paul Gortmaker wrote: > On 28/09/2015 (Mon 23:09) Geert Uytterhoeven wrote: > > > Hi Paul, ... > > > > Why did you choose this approach? > > What about changing the "bool"s to "tristate"s in Kconfig instead? > > Long answer is here: > >

Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular

[Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular] On 29/09/2015 (Tue 16:32) Finn Thain wrote: > > Hi Paul, > > On Mon, 28 Sep 2015, Paul Gortmaker wrote: > > > On 28/09/2015 (Mon 23:09) Geert Uytterhoeven wrote: > > > > > Hi Paul, &

Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular

Hi Paul, On Mon, Sep 28, 2015 at 9:51 PM, Paul Gortmaker wrote: > In a previous merge window, we made changes to allow better > delineation between modular and non-modular code in commit > 0fd972a7d91d6e15393c449492a04d94c0b89351 ("module: relocate module_init >

Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular

[Re: [PATCH net-next 0/6] make non-modular code explicitly non-modular] On 28/09/2015 (Mon 23:09) Geert Uytterhoeven wrote: > Hi Paul, > > On Mon, Sep 28, 2015 at 9:51 PM, Paul Gortmaker > <paul.gortma...@windriver.com> wrote: > > In a previous merge window, we made