From: Chao Yu <yuchao0@huawei.com>
To: Yi Zhuang <zhuangyi1@huawei.com>, <jaegeuk@kernel.org>,
<chao@kernel.org>, <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH -next] f2fs: modify open brace '{' following function definitions
Date: Tue, 6 Apr 2021 17:30:12 +0800 [thread overview]
Message-ID: <6e60ba49-8e1d-e9db-7b66-d1a67db5cd0f@huawei.com> (raw)
In-Reply-To: <20210406014735.127457-1-zhuangyi1@huawei.com>
On 2021/4/6 9:47, Yi Zhuang wrote:
> 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>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-04-06 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 1:47 [f2fs-dev] [PATCH -next] f2fs: modify open brace '{' following function definitions Yi Zhuang
2021-04-06 9:30 ` Chao Yu [this message]
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=6e60ba49-8e1d-e9db-7b66-d1a67db5cd0f@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zhuangyi1@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).