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

From	David Miller <davem@davemloft.net>
Newsgroups	linux.kernel
Subject	Re: [PATCH -next] bpf: make inode code explicitly non-modular
Date	2016-07-11 23:00 +0200
Message-ID	<rTQt4-3Fx-29@gated-at.bofh.it> (permalink)
References	<rTMIO-1g9-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

From: Paul Gortmaker <paul.gortmaker@windriver.com>
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 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 <ast@kernel.org>
> Cc: netdev@vger.kernel.org
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

Applied.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH -next] bpf: make inode code explicitly non-modular Paul Gortmaker <paul.gortmaker@windriver.com> - 2016-07-11 19:00 +0200
  Re: [PATCH -next] bpf: make inode code explicitly non-modular Daniel Borkmann <daniel@iogearbox.net> - 2016-07-11 19:30 +0200
  Re: [PATCH -next] bpf: make inode code explicitly non-modular David Miller <davem@davemloft.net> - 2016-07-11 23:00 +0200

csiph-web