All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH -next] fs/omfs: convert comma to semicolon
Date: Sun, 13 Dec 2020 16:30:44 -0500	[thread overview]
Message-ID: <20201213213044.GA9300@bobcopeland.com> (raw)
In-Reply-To: <20201211083930.1825-1-zhengyongjun3@huawei.com>

On Fri, Dec 11, 2020 at 04:39:30PM +0800, Zheng Yongjun wrote:
> Replace a comma between expression statements by a semicolon.
> 
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>

Acked-by: Bob Copeland <me@bobcopeland.com>

As I do not run a git tree specifically for OMFS, this should
probably go through vfs tree.

> ---
>  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);
>  }
> -- 
> 2.22.0

-- 
Bob Copeland %% https://bobcopeland.com/

  reply	other threads:[~2020-12-13 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  8:39 [PATCH -next] fs/omfs: convert comma to semicolon Zheng Yongjun
2020-12-13 21:30 ` Bob Copeland [this message]
2020-12-11  8:40 Zheng Yongjun
2020-12-11 12:22 ` Jeff Layton

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=20201213213044.GA9300@bobcopeland.com \
    --to=me@bobcopeland.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.