Re: [PATCH -next] bpf: make inode code explicitly non-modular

2016-07-11 Thread David Miller
From: Paul Gortmaker Date: Mon, 11 Jul 2016 12:51:01 -0400 > The Kconfig currently controlling compilation of this code is: > > init/Kconfig:config BPF_SYSCALL > init/Kconfig: bool "Enable bpf() system call" > > ...meaning that it currently is not being built as a module by anyone. > > Lets

Re: [PATCH -next] bpf: make inode code explicitly non-modular

2016-07-11 Thread Daniel Borkmann
On 07/11/2016 06:51 PM, Paul Gortmaker wrote: The Kconfig currently controlling compilation of this code is: init/Kconfig:config BPF_SYSCALL init/Kconfig: bool "Enable bpf() system call" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of m

[PATCH -next] bpf: make inode code explicitly non-modular

2016-07-11 Thread Paul Gortmaker
The Kconfig currently controlling compilation of this code is: init/Kconfig:config BPF_SYSCALL init/Kconfig: bool "Enable bpf() system call" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modular infrastructure use, so that when reading