From: Chao Yu <yuchao0@huawei.com>
To: YueHaibing <yuehaibing@huawei.com>, <jaegeuk@kernel.org>,
<chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH -next] f2fs: remove set but not used variable 'cs_block'
Date: Thu, 26 Dec 2019 11:44:43 +0800 [thread overview]
Message-ID: <673efe18-d528-2e9b-6d44-a6a7a22086f3@huawei.com> (raw)
In-Reply-To: <20191224124359.15040-1-yuehaibing@huawei.com>
On 2019/12/24 20:43, YueHaibing wrote:
> fs/f2fs/segment.c: In function fix_curseg_write_pointer:
> fs/f2fs/segment.c:4485:35: warning: variable cs_block set but not used [-Wunused-but-set-variable]
>
> It is never used since commit 362d8a920384 ("f2fs: Check
> write pointer consistency of open zones") , so remove it.
Thanks for the fix!
Do you mind merging this patch to original patch? as it's still
pending in dev branch.
Thanks,
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> fs/f2fs/segment.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index a951953..72cf257 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -4482,14 +4482,13 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)
> struct f2fs_dev_info *zbd;
> struct blk_zone zone;
> unsigned int cs_section, wp_segno, wp_blkoff, wp_sector_off;
> - block_t cs_zone_block, wp_block, cs_block;
> + block_t cs_zone_block, wp_block;
> unsigned int log_sectors_per_block = sbi->log_blocksize - SECTOR_SHIFT;
> sector_t zone_sector;
> int err;
>
> cs_section = GET_SEC_FROM_SEG(sbi, cs->segno);
> cs_zone_block = START_BLOCK(sbi, GET_SEG_FROM_SEC(sbi, cs_section));
> - cs_block = START_BLOCK(sbi, cs->segno) + cs->next_blkoff;
>
> zbd = get_target_zoned_dev(sbi, cs_zone_block);
> if (!zbd)
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-12-26 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 12:43 [f2fs-dev] [PATCH -next] f2fs: remove set but not used variable 'cs_block' YueHaibing
2019-12-26 3:44 ` Chao Yu [this message]
2019-12-26 6:05 ` Yuehaibing
2019-12-26 8:24 ` Shinichiro Kawasaki
2020-01-15 2:33 ` Shinichiro Kawasaki
2020-01-15 9:54 ` Chao Yu
2020-01-16 0:25 ` Shinichiro Kawasaki
2020-01-15 21:44 ` 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=673efe18-d528-2e9b-6d44-a6a7a22086f3@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@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).