From: Jan Kara <jack@suse.cz>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: jack@suse.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] mm/fs: remove variable bdi set but not used
Date: Thu, 3 Feb 2022 09:06:49 +0100 [thread overview]
Message-ID: <20220203080649.5q4c7rvowwgf4ssp@quack3.lan> (raw)
In-Reply-To: <20220203052633.54000-1-yang.lee@linux.alibaba.com>
On Thu 03-02-22 13:26:33, Yang Li wrote:
> The code that uses the pointer 'bdi' has been removed in commit:
> '37c32ade079f000c8e539730f254b14fae0d3b49' and inode_to_bdi() doesn't
> change 'inode', so the declaration and assignment of 'bdi' can be removed.
>
> Eliminate the following clang warning:
> fs/ext2/ialloc.c:173:27: warning: variable 'bdi' set but not used
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Thanks! The patch looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext2/ialloc.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/fs/ext2/ialloc.c b/fs/ext2/ialloc.c
> index d632764da240..998dd2ac8008 100644
> --- a/fs/ext2/ialloc.c
> +++ b/fs/ext2/ialloc.c
> @@ -170,9 +170,6 @@ static void ext2_preread_inode(struct inode *inode)
> unsigned long offset;
> unsigned long block;
> struct ext2_group_desc * gdp;
> - struct backing_dev_info *bdi;
> -
> - bdi = inode_to_bdi(inode);
>
> block_group = (inode->i_ino - 1) / EXT2_INODES_PER_GROUP(inode->i_sb);
> gdp = ext2_get_group_desc(inode->i_sb, block_group, NULL);
> --
> 2.20.1.7.g153144c
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2022-02-03 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 5:26 [PATCH -next] mm/fs: remove variable bdi set but not used Yang Li
2022-02-03 8:06 ` Jan Kara [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=20220203080649.5q4c7rvowwgf4ssp@quack3.lan \
--to=jack@suse.cz \
--cc=abaci@linux.alibaba.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yang.lee@linux.alibaba.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