From: DongOh Shin <doscode.kr@gmail.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com
Cc: doscode.kr@gmail.com, linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 2/5] Fix coding style error in f2fs.h
Date: Fri, 27 Jan 2017 10:29:37 -0800 [thread overview]
Message-ID: <20170127182940.11389-3-doscode.kr@gmail.com> (raw)
In-Reply-To: <20170127182940.11389-1-doscode.kr@gmail.com>
A coding style error below has been resolved:
"space prohibited before that ',' (ctx:WxW)"
Signed-off-by: DongOh Shin <doscode.kr@gmail.com>
---
fs/f2fs/f2fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 5d257a9..85bd8c1 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -2023,7 +2023,7 @@ void f2fs_set_link(struct inode *, struct f2fs_dir_entry *,
struct page *, struct inode *);
int update_dent_inode(struct inode *, struct inode *, const struct qstr *);
void f2fs_update_dentry(nid_t ino, umode_t mode, struct f2fs_dentry_ptr *,
- const struct qstr *, f2fs_hash_t , unsigned int);
+ const struct qstr *, f2fs_hash_t, unsigned int);
int f2fs_add_regular_entry(struct inode *, const struct qstr *,
const struct qstr *, struct inode *, nid_t, umode_t);
int __f2fs_do_add_link(struct inode *, struct fscrypt_name*, struct inode *,
--
1.8.3.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-01-27 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 18:29 [PATCH 0/5] Fix coding style errors and warnings in f2fs.h DongOh Shin
2017-01-27 18:29 ` [PATCH 1/5] Fix coding style errors " DongOh Shin
2017-01-27 18:29 ` DongOh Shin [this message]
2017-01-27 18:29 ` [PATCH 3/5] Fix coding style warnings " DongOh Shin
2017-01-27 18:29 ` [PATCH 4/5] " DongOh Shin
2017-01-27 18:29 ` [PATCH 5/5] " DongOh Shin
2017-01-29 4:23 ` [PATCH 0/5] Fix coding style errors and " Jaegeuk Kim
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=20170127182940.11389-3-doscode.kr@gmail.com \
--to=doscode.kr@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).