From: Chihau Chau <chihau@gmail.com>
To: jmorris@namei.org
Cc: eparis@redhat.com, viro@zeniv.linux.org.uk,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Chihau Chau <chihau@gmail.com>
Subject: [PATCH] Security: inode: Fix code style issues
Date: Thu, 22 Apr 2010 20:37:15 -0400 [thread overview]
Message-ID: <1271983035-26401-1-git-send-email-chihau@gmail.com> (raw)
From: Chihau Chau <chihau@gmail.com>
This fixes two code style issues:
- A space required after that close brace '}'
- A space required after that ','
Signed-off-by: Chihau Chau <chihau@gmail.com>
---
security/inode.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/inode.c b/security/inode.c
index c3a7938..f875f47 100644
--- a/security/inode.c
+++ b/security/inode.c
@@ -124,7 +124,7 @@ static inline int positive(struct dentry *dentry)
static int fill_super(struct super_block *sb, void *data, int silent)
{
- static struct tree_descr files[] = {{""}};
+ static struct tree_descr files[] = { {""} };
return simple_fill_super(sb, SECURITYFS_MAGIC, files);
}
@@ -208,7 +208,7 @@ struct dentry *securityfs_create_file(const char *name, mode_t mode,
struct dentry *dentry = NULL;
int error;
- pr_debug("securityfs: creating file '%s'\n",name);
+ pr_debug("securityfs: creating file '%s'\n", name);
error = simple_pin_fs(&fs_type, &mount, &mount_count);
if (error) {
--
1.5.6.3
next reply other threads:[~2010-04-23 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 0:37 Chihau Chau [this message]
2010-04-23 15:50 ` [PATCH] Security: inode: Fix code style issues Randy Dunlap
2010-04-23 16:10 ` Chihau Chau
2010-04-23 16:35 ` Randy Dunlap
2010-04-23 18:31 ` Chihau Chau
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=1271983035-26401-1-git-send-email-chihau@gmail.com \
--to=chihau@gmail.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.