From: Yi Zhuang <zhuangyi1@huawei.com>
To: <jaegeuk@kernel.org>, <chao@kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] [PATCH -next] f2fs: modify open brace '{' following function definitions
Date: Tue, 6 Apr 2021 09:47:35 +0800 [thread overview]
Message-ID: <20210406014735.127457-1-zhuangyi1@huawei.com> (raw)
Made suggested modifications from checkpatch in reference to ERROR:
open brace '{' following function definitions go on the next line
Signed-off-by: Yi Zhuang <zhuangyi1@huawei.com>
---
fs/f2fs/segment.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 213cc1b8279a..301121dc9f75 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -4764,7 +4764,8 @@ static struct f2fs_dev_info *get_target_zoned_dev(struct f2fs_sb_info *sbi,
}
static int report_one_zone_cb(struct blk_zone *zone, unsigned int idx,
- void *data) {
+ void *data)
+{
memcpy(data, zone, sizeof(struct blk_zone));
return 0;
}
@@ -4880,7 +4881,8 @@ struct check_zone_write_pointer_args {
};
static int check_zone_write_pointer_cb(struct blk_zone *zone, unsigned int idx,
- void *data) {
+ void *data)
+{
struct check_zone_write_pointer_args *args;
args = (struct check_zone_write_pointer_args *)data;
--
2.26.0.106.g9fadedd
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2021-04-06 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 1:47 Yi Zhuang [this message]
2021-04-06 9:30 ` [f2fs-dev] [PATCH -next] f2fs: modify open brace '{' following function definitions Chao Yu
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=20210406014735.127457-1-zhuangyi1@huawei.com \
--to=zhuangyi1@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).