From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jfs: remove redundant assignments to ipaimap and ipaimap2
Date: Mon, 17 Oct 2022 17:39:59 -0500 [thread overview]
Message-ID: <f31307ae-8413-d25a-d602-76016a52f7a7@oracle.com> (raw)
In-Reply-To: <20221017215636.863916-1-colin.i.king@gmail.com>
On 10/17/22 4:56PM, Colin Ian King wrote:
> The pointers ipaimap and ipaimap2 are initialized with values that are
> never read, they are re-assigned later when they are required. The
> initializations are redundant and can be removed.
Hmm. Or we can remove the later assignments. That would seem more
consistent with the ipbmap and ipimap.
>
> Cleans up two clang scan build warnings:
> fs/jfs/jfs_umount.c:42:16: warning: Value stored to 'ipaimap' during
> its initialization is never read [deadcode.DeadStores]
>
> fs/jfs/jfs_umount.c:43:16: warning: Value stored to 'ipaimap2' during
> its initialization is never read [deadcode.DeadStores]
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> fs/jfs/jfs_umount.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/jfs/jfs_umount.c b/fs/jfs/jfs_umount.c
> index 3e8b13e6aa01..cc4d7e6e8a4b 100644
> --- a/fs/jfs/jfs_umount.c
> +++ b/fs/jfs/jfs_umount.c
> @@ -39,8 +39,8 @@ int jfs_umount(struct super_block *sb)
> struct jfs_sb_info *sbi = JFS_SBI(sb);
> struct inode *ipbmap = sbi->ipbmap;
> struct inode *ipimap = sbi->ipimap;
> - struct inode *ipaimap = sbi->ipaimap;
> - struct inode *ipaimap2 = sbi->ipaimap2;
> + struct inode *ipaimap;
> + struct inode *ipaimap2;
> struct jfs_log *log;
> int rc = 0;
>
prev parent reply other threads:[~2022-10-17 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:56 Colin Ian King
2022-10-17 22:39 ` Dave Kleikamp [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=f31307ae-8413-d25a-d602-76016a52f7a7@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@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
all inboxes | Powered by JetHome®