From: John Johansen <john.johansen@canonical.com>
To: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org, Shan Wei <shanwei@cn.fujitsu.com>
Subject: [PATCH 3/3] AppArmor: kill unused macros in lsm.c
Date: Tue, 8 Mar 2011 11:03:09 -0800 [thread overview]
Message-ID: <1299610989-3917-4-git-send-email-john.johansen@canonical.com> (raw)
In-Reply-To: <1299610989-3917-1-git-send-email-john.johansen@canonical.com>
Remove unused macros.
V3: param_check_aabool, param_check_aauint and param_check_aalockpolicy
are used by module_param_named implicitly.
Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
Signed-off-by: John Johansen <john.johansen@canonical.com>
---
security/apparmor/lsm.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/security/apparmor/lsm.c b/security/apparmor/lsm.c
index b7106f1..d21a427 100644
--- a/security/apparmor/lsm.c
+++ b/security/apparmor/lsm.c
@@ -693,11 +693,9 @@ static struct kernel_param_ops param_ops_aalockpolicy = {
static int param_set_audit(const char *val, struct kernel_param *kp);
static int param_get_audit(char *buffer, struct kernel_param *kp);
-#define param_check_audit(name, p) __param_check(name, p, int)
static int param_set_mode(const char *val, struct kernel_param *kp);
static int param_get_mode(char *buffer, struct kernel_param *kp);
-#define param_check_mode(name, p) __param_check(name, p, int)
/* Flag values, also controllable via /sys/module/apparmor/parameters
* We define special types as we want to do additional mediation.
--
1.7.1
next prev parent reply other threads:[~2011-03-08 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 19:03 [AppArmor 0/3] Cleanups to AppArmor's build John Johansen
2011-03-08 19:03 ` [PATCH 1/3] AppArmor: Cleanup make file to remove cruft and make it easier to read John Johansen
2011-03-08 19:03 ` [PATCH 2/3] AppArmor: cleanup generated files correctly John Johansen
2011-03-08 19:03 ` John Johansen [this message]
2011-03-08 23:32 ` [AppArmor 0/3] Cleanups to AppArmor's build James Morris
2011-03-09 1:27 ` John Johansen
2011-03-09 3:14 ` James Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1299610989-3917-4-git-send-email-john.johansen@canonical.com \
--to=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®