Re: [PATCH] fs/crypto: make crypto.c explicitly non-modular

2016-03-02 Thread Jaegeuk Kim
Hi Paul, On Mon, Feb 29, 2016 at 09:31:59AM -0500, Paul Gortmaker wrote: > [Re: [PATCH] fs/crypto: make crypto.c explicitly non-modular] On 29/02/2016 > (Mon 10:56) Arnd Bergmann wrote: > > > On Saturday 27 February 2016 15:20:49 Paul Gortmaker wrote: >

Re: [PATCH] fs/crypto: make crypto.c explicitly non-modular

2016-02-29 Thread Paul Gortmaker
[Re: [PATCH] fs/crypto: make crypto.c explicitly non-modular] On 29/02/2016 (Mon 10:56) Arnd Bergmann wrote: > On Saturday 27 February 2016 15:20:49 Paul Gortmaker wrote: > > As of commit 47134e6084f70fdf4381af75d4569cec6c7ebd50 ("fs crypto: > > add Makefile and Kconfig

Re: [PATCH] fs/crypto: make crypto.c explicitly non-modular

2016-02-29 Thread Arnd Bergmann
On Saturday 27 February 2016 15:20:49 Paul Gortmaker wrote: > As of commit 47134e6084f70fdf4381af75d4569cec6c7ebd50 ("fs crypto: > add Makefile and Kconfig") the compile of fs/crypto/crypto.c tripped > my local audit for non-modules using modular infrastructure vs. their > built in counterparts. >

[PATCH] fs/crypto: make crypto.c explicitly non-modular

2016-02-27 Thread Paul Gortmaker
As of commit 47134e6084f70fdf4381af75d4569cec6c7ebd50 ("fs crypto: add Makefile and Kconfig") the compile of fs/crypto/crypto.c tripped my local audit for non-modules using modular infrastructure vs. their built in counterparts. The Kconfig currently controlling compilation of this code is: confi