From: eparis@redhat.com
To: linux-kernel@vger.kernel.org
Cc: jmorris@namei.org, serue@us.ibm.com, Eric Paris <eparis@redhat.com>
Subject: [PATCH 2/4] capability: security/capability.c whitespace, syntax, and other cleanups
Date: Wed, 23 Apr 2008 13:52:32 -0400 [thread overview]
Message-ID: <12089731553297-git-send-email-eparis@redhat.com> (raw)
In-Reply-To: <12089731541206-git-send-email-eparis@redhat.com>
From: Eric Paris <eparis@redhat.com>
This patch changes security/capability.c to fix whitespace and syntax issues. Things that
are fixed may include (does not not have to include)
whitespace at end of lines
spaces followed by tabs
spaces used instead of tabs
spacing around parenthesis
location of { around structs and else clauses
location of * in pointer declarations
removal of initialization of static data to keep it in the right section
useless {} in if statemetns
useless checking for NULL before kfree
fixing of the indentation depth of switch statements
no assignments in if statements
include spaces around , in function calls
and any number of other things I forgot to mention
Signed-off-by: Eric Paris <eparis@redhat.com>
---
security/capability.c | 20 ++++++++++----------
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/security/capability.c b/security/capability.c
index 2c6e06d..e77d5e4 100644
--- a/security/capability.c
+++ b/security/capability.c
@@ -46,9 +46,9 @@ static struct security_operations capability_ops = {
.task_post_setuid = cap_task_post_setuid,
.task_reparent_to_init = cap_task_reparent_to_init,
- .syslog = cap_syslog,
+ .syslog = cap_syslog,
- .vm_enough_memory = cap_vm_enough_memory,
+ .vm_enough_memory = cap_vm_enough_memory,
};
/* flag to keep track of how we were registered */
@@ -57,25 +57,25 @@ static int secondary;
static int capability_disable;
module_param_named(disable, capability_disable, int, 0);
-static int __init capability_init (void)
+static int __init capability_init(void)
{
if (capability_disable) {
printk(KERN_INFO "Capabilities disabled at initialization\n");
return 0;
}
/* register ourselves with the security framework */
- if (register_security (&capability_ops)) {
+ if (register_security(&capability_ops)) {
/* try registering with primary module */
- if (mod_reg_security (KBUILD_MODNAME, &capability_ops)) {
- printk (KERN_INFO "Failure registering capabilities "
- "with primary security module.\n");
+ if (mod_reg_security(KBUILD_MODNAME, &capability_ops)) {
+ printk(KERN_INFO "Failure registering capabilities "
+ "with primary security module.\n");
return -EINVAL;
}
secondary = 1;
}
- printk (KERN_INFO "Capability LSM initialized%s\n",
- secondary ? " as secondary" : "");
+ printk(KERN_INFO "Capability LSM initialized%s\n",
+ secondary ? " as secondary" : "");
return 0;
}
-security_initcall (capability_init);
+security_initcall(capability_init);
--
1.5.2.1
next prev parent reply other threads:[~2008-04-23 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 17:52 [PATCH 1/4] capability: capability.h whitespace, syntax, and other cleanups eparis
2008-04-23 17:52 ` eparis [this message]
2008-04-23 17:52 ` [PATCH 3/4] capability: kernel/capability.c " eparis
2008-04-23 17:52 ` [PATCH 4/4] capability: commoncap.c " eparis
2008-04-24 1:54 ` [PATCH 1/4] capability: capability.h " Serge E. Hallyn
2008-04-24 12:13 ` Eric Paris
2008-04-24 12:26 ` Serge E. Hallyn
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=12089731553297-git-send-email-eparis@redhat.com \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.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