From: Chao Yu <chao@kernel.org>
To: Colin King <colin.king@canonical.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH][f2fs-next] f2fs: remove several redundant assignments
Date: Sun, 22 Oct 2017 22:57:59 +0800 [thread overview]
Message-ID: <bf9d1036-e07d-5d61-bba7-cb931d00016a@kernel.org> (raw)
In-Reply-To: <20171019105821.336-1-colin.king@canonical.com>
On 2017/10/19 18:58, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are several assignments to variables that are redundant
> as the values are never read when the variables are updated later
> and so the redundant statements can be safely removed.
>
> Cleans up clang warnings:
> fs/f2fs/segment.c:923:19: warning: Value stored to 'p' during its initialization is never read
> fs/f2fs/segment.c:2060:2: warning: Value stored to 'hint' is never read
> fs/f2fs/segment.c:2353:2: warning: Value stored to 'start_block' is never read
> fs/f2fs/segment.c:2354:2: warning: Value stored to 'end_block' is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
> ---
> fs/f2fs/segment.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index bfbcff8339c5..df7af294c1e0 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -920,7 +920,7 @@ static struct discard_cmd *__insert_discard_tree(struct f2fs_sb_info *sbi,
> struct rb_node *insert_parent)
> {
> struct discard_cmd_control *dcc = SM_I(sbi)->dcc_info;
> - struct rb_node **p = &dcc->root.rb_node;
> + struct rb_node **p;
> struct rb_node *parent = NULL;
> struct discard_cmd *dc = NULL;
>
> @@ -2057,7 +2057,6 @@ static void get_new_segment(struct f2fs_sb_info *sbi,
> }
> secno = left_start;
> skip_left:
> - hint = secno;
> segno = GET_SEG_FROM_SEC(sbi, secno);
> zoneno = GET_ZONE_FROM_SEC(sbi, secno);
>
> @@ -2350,9 +2349,6 @@ int f2fs_trim_fs(struct f2fs_sb_info *sbi, struct fstrim_range *range)
> end_segno = (end >= MAX_BLKADDR(sbi)) ? MAIN_SEGS(sbi) - 1 :
> GET_SEGNO(sbi, end);
>
> - start_block = START_BLOCK(sbi, start_segno);
> - end_block = START_BLOCK(sbi, end_segno + 1);
> -
> cpc.reason = CP_DISCARD;
> cpc.trim_minlen = max_t(__u64, 1, F2FS_BYTES_TO_BLK(range->minlen));
>
>
prev parent reply other threads:[~2017-10-22 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 10:58 [PATCH][f2fs-next] f2fs: remove several redundant assignments Colin King
2017-10-22 14:57 ` Chao Yu [this message]
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=bf9d1036-e07d-5d61-bba7-cb931d00016a@kernel.org \
--to=chao@kernel.org \
--cc=colin.king@canonical.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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).