summaryrefslogtreecommitdiff
path: root/security/apparmor/crypto.c
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2018-12-09 23:36:31 +0300
committerJames Morris <james.morris@microsoft.com>2018-12-13 01:58:51 +0300
commit1072bd678547f8663cfb81a22fdb50c589e4976e (patch)
tree7d5ed4769484178916f6aa74faaf73371169cc2f /security/apparmor/crypto.c
parent876979c9308b7228cdaf6785909c57eebc85d911 (diff)
downloadlinux-1072bd678547f8663cfb81a22fdb50c589e4976e.tar.xz
security: fs: make inode explicitly non-modular
The Makefile/Kconfig entry controlling compilation of this code is: security/Makefile:obj-$(CONFIG_SECURITYFS) += inode.o security/Kconfig:config SECURITYFS security/Kconfig: bool "Enable the securityfs filesystem" ...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. We also delete the MODULE_LICENSE tag etc. since all that information is already contained at the top of the file in the comments. The removal of module.h uncovered a couple previously hidden implicit header requirements which are now included explicitly. Cc: James Morris <jmorris@namei.org> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: linux-security-module@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: James Morris <james.morris@microsoft.com>
Diffstat (limited to 'security/apparmor/crypto.c')
0 files changed, 0 insertions, 0 deletions