From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Colin Ian King <colin.i.king@gmail.com>,
jfs-discussion@lists.sourceforge.net
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] jfs: remove redundant assignments to ipaimap and ipaimap2
Date: Tue, 18 Oct 2022 10:44:30 -0500 [thread overview]
Message-ID: <2c02b2de-4fb3-1ad2-5a30-614f9550c108@oracle.com> (raw)
In-Reply-To: <20221018152310.941770-1-colin.i.king@gmail.com>
Looks good. Applied.
Thanks,
Shaggy
On 10/18/22 10:23AM, Colin Ian King wrote:
> The pointers ipaimap and ipaimap2 are re-assigned with values a second
> time with the same values when they were initialized. The re-assignments
> are redundant and can be removed.
>
> 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>
> ---
> V2: remove re-assignments rather than initializations as per the
> recommendation from Dave Kleikamp
> ---
> fs/jfs/jfs_umount.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/jfs/jfs_umount.c b/fs/jfs/jfs_umount.c
> index 3e8b13e6aa01..95ebcd17ce75 100644
> --- a/fs/jfs/jfs_umount.c
> +++ b/fs/jfs/jfs_umount.c
> @@ -68,7 +68,6 @@ int jfs_umount(struct super_block *sb)
> /*
> * close secondary aggregate inode allocation map
> */
> - ipaimap2 = sbi->ipaimap2;
> if (ipaimap2) {
> diUnmount(ipaimap2, 0);
> diFreeSpecial(ipaimap2);
> @@ -78,7 +77,6 @@ int jfs_umount(struct super_block *sb)
> /*
> * close aggregate inode allocation map
> */
> - ipaimap = sbi->ipaimap;
> diUnmount(ipaimap, 0);
> diFreeSpecial(ipaimap);
> sbi->ipaimap = NULL;
prev parent reply other threads:[~2022-10-18 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:23 Colin Ian King
2022-10-18 15:44 ` 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=2c02b2de-4fb3-1ad2-5a30-614f9550c108@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=colin.i.king@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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®