linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/2] f2fs: add braces for macro variables more
Date: Sat, 22 Apr 2017 08:30:01 +0800	[thread overview]
Message-ID: <ed638ae8-e40b-9160-c06a-0b69e01ae2a2@huawei.com> (raw)
In-Reply-To: <20170421004957.23760-1-jaegeuk@kernel.org>

On 2017/4/21 8:49, Jaegeuk Kim wrote:
> This patch adds braces for macro variables more in include/linux/f2fs_fs.h.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
>  fs/f2fs/f2fs.h          |  1 +
>  include/linux/f2fs_fs.h | 10 +++++-----
>  2 files changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index e2d9a8d9101e..ca647d264b61 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -16,6 +16,7 @@
>  #include <linux/buffer_head.h>
>  #include <linux/slab.h>
>  #include <linux/crc32.h>
> +#include <linux/quota.h>

This is no needed. ;)

Thanks,

>  #include <linux/magic.h>
>  #include <linux/kobject.h>
>  #include <linux/sched.h>
> diff --git a/include/linux/f2fs_fs.h b/include/linux/f2fs_fs.h
> index e2d239ed4c60..639cbdf65e2b 100644
> --- a/include/linux/f2fs_fs.h
> +++ b/include/linux/f2fs_fs.h
> @@ -32,9 +32,9 @@
>  /* 0, 1(node nid), 2(meta nid) are reserved node id */
>  #define F2FS_RESERVED_NODE_NUM		3
>  
> -#define F2FS_ROOT_INO(sbi)	(sbi->root_ino_num)
> -#define F2FS_NODE_INO(sbi)	(sbi->node_ino_num)
> -#define F2FS_META_INO(sbi)	(sbi->meta_ino_num)
> +#define F2FS_ROOT_INO(sbi)	((sbi)->root_ino_num)
> +#define F2FS_NODE_INO(sbi)	((sbi)->node_ino_num)
> +#define F2FS_META_INO(sbi)	((sbi)->meta_ino_num)
>  
>  #define F2FS_IO_SIZE(sbi)	(1 << (sbi)->write_io_size_bits) /* Blocks */
>  #define F2FS_IO_SIZE_KB(sbi)	(1 << ((sbi)->write_io_size_bits + 2)) /* KB */
> @@ -161,7 +161,7 @@ struct f2fs_checkpoint {
>   */
>  #define F2FS_ORPHANS_PER_BLOCK	1020
>  
> -#define GET_ORPHAN_BLOCKS(n)	((n + F2FS_ORPHANS_PER_BLOCK - 1) / \
> +#define GET_ORPHAN_BLOCKS(n)	(((n) + F2FS_ORPHANS_PER_BLOCK - 1) / \
>  					F2FS_ORPHANS_PER_BLOCK)
>  
>  struct f2fs_orphan_block {
> @@ -449,7 +449,7 @@ typedef __le32	f2fs_hash_t;
>  #define F2FS_SLOT_LEN		8
>  #define F2FS_SLOT_LEN_BITS	3
>  
> -#define GET_DENTRY_SLOTS(x)	((x + F2FS_SLOT_LEN - 1) >> F2FS_SLOT_LEN_BITS)
> +#define GET_DENTRY_SLOTS(x) (((x) + F2FS_SLOT_LEN - 1) >> F2FS_SLOT_LEN_BITS)
>  
>  /* MAX level for dir lookup */
>  #define MAX_DIR_HASH_DEPTH	63
> 

  parent reply	other threads:[~2017-04-22  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  0:49 [PATCH 1/2] f2fs: add braces for macro variables more Jaegeuk Kim
2017-04-21  0:49 ` [PATCH 2/2] f2fs: fix out-of free segments Jaegeuk Kim
2017-04-22  0:30 ` Chao Yu [this message]
2017-04-24 17:38   ` [PATCH 1/2] f2fs: add braces for macro variables more Jaegeuk Kim

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=ed638ae8-e40b-9160-c06a-0b69e01ae2a2@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).