Re: [PATCH -next] bpf: make inode code explicitly non-modular
From: Paul GortmakerDate: 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 remove the couple traces of modular infrastructure use, so that > when reading the driver there is no doubt it is builtin-only. > > Note that MODULE_ALIAS is a no-op for non-modular code. > > We replace module.h with init.h since the file does use __init. > > Cc: Alexei Starovoitov > Cc: netdev@vger.kernel.org > Signed-off-by: Paul Gortmaker Applied.
Re: [PATCH -next] bpf: make inode code explicitly non-modular
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 modular infrastructure use, so that when reading the driver there is no doubt it is builtin-only. Note that MODULE_ALIAS is a no-op for non-modular code. We replace module.h with init.h since the file does use __init. Cc: Alexei StarovoitovCc: netdev@vger.kernel.org Signed-off-by: Paul Gortmaker (Patch is for net-next tree then.) Acked-by: Daniel Borkmann