From: Jeff Layton <jlayton@kernel.org>
To: Zheng Yongjun <zhengyongjun3@huawei.com>, idryomov@gmail.com
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
me <me@bobcopeland.com>,
linux-karma-devel <linux-karma-devel@lists.sourceforge.net>
Subject: Re: [PATCH -next] fs/omfs: convert comma to semicolon
Date: Fri, 11 Dec 2020 07:22:58 -0500 [thread overview]
Message-ID: <0cde2f2eecffacc754d09e1f5c2bc338ede6451f.camel@kernel.org> (raw)
In-Reply-To: <20201211084013.1878-1-zhengyongjun3@huawei.com>
On Fri, 2020-12-11 at 16:40 +0800, Zheng Yongjun wrote:
> Replace a comma between expression statements by a semicolon.
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
> ---
> fs/omfs/file.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/omfs/file.c b/fs/omfs/file.c
> index 2c7b70ee1388..fc6828f30f60 100644
> --- a/fs/omfs/file.c
> +++ b/fs/omfs/file.c
> @@ -22,8 +22,8 @@ void omfs_make_empty_table(struct buffer_head *bh, int offset)
> struct omfs_extent *oe = (struct omfs_extent *) &bh->b_data[offset];
>
>
> oe->e_next = ~cpu_to_be64(0ULL);
> - oe->e_extent_count = cpu_to_be32(1),
> - oe->e_fill = cpu_to_be32(0x22),
> + oe->e_extent_count = cpu_to_be32(1);
> + oe->e_fill = cpu_to_be32(0x22);
> oe->e_entry.e_cluster = ~cpu_to_be64(0ULL);
> oe->e_entry.e_blocks = ~cpu_to_be64(0ULL);
> }
(cc'ing Bob Copeland and linux-karma mailing list)
Looks fine, but this patch isn't related to ceph in any way. See
Documentation/filesystems/omfs.rst for a description of OMFS.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-12-11 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 8:40 [PATCH -next] fs/omfs: convert comma to semicolon Zheng Yongjun
2020-12-11 12:22 ` Jeff Layton [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-11 8:39 Zheng Yongjun
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=0cde2f2eecffacc754d09e1f5c2bc338ede6451f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-karma-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=zhengyongjun3@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).