linux-kernel - Re: [PATCH -next] fs/omfs: convert comma to semicolon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0cde2f2eecffacc754d09e1f5c2bc338ede6451f.camel@kernel.org>
Date:   Fri, 11 Dec 2020 07:22:58 -0500
From:   Jeff Layton <jlayton@...nel.org>
To:     Zheng Yongjun <zhengyongjun3@...wei.com>, idryomov@...il.com
Cc:     ceph-devel@...r.kernel.org, linux-kernel@...r.kernel.org,
        me <me@...copeland.com>,
        linux-karma-devel <linux-karma-devel@...ts.sourceforge.net>
Subject: Re: [PATCH -next] fs/omfs: convert comma to semicolon

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@...wei.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@...nel.org>