mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Colin Ian King <colin.i.king@gmail.com>,
	Christian Brauner <brauner@kernel.org>,
	jfs-discussion@lists.sourceforge.net
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next][V2] jfs: remove redundant initialization to pointer ip
Date: Tue, 29 Aug 2023 12:21:51 -0500	[thread overview]
Message-ID: <6974c489-3238-4037-81e5-3d9ec5e48ee0@oracle.com> (raw)
In-Reply-To: <20230818150210.1208746-1-colin.i.king@gmail.com>

On 8/18/23 10:02AM, Colin Ian King wrote:
> The pointer ip is being initialized with a value that is never read, it
> is being re-assigned later on. The assignment is redundant and can be
> removed.  Cleans up clang scan warning:
> 
> fs/jfs/namei.c:886:16: warning: Value stored to 'ip' during its
> initialization is never read [deadcode.DeadStores]

Looks good. Applied.

> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> 
> V2: fix commit message "uninitialized" -> "initialized"
> 
> ---
>   fs/jfs/namei.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/jfs/namei.c b/fs/jfs/namei.c
> index 029d47065600..57d7a4300210 100644
> --- a/fs/jfs/namei.c
> +++ b/fs/jfs/namei.c
> @@ -883,7 +883,7 @@ static int jfs_symlink(struct mnt_idmap *idmap, struct inode *dip,
>   	struct component_name dname;
>   	u32 ssize;		/* source pathname size */
>   	struct btstack btstack;
> -	struct inode *ip = d_inode(dentry);
> +	struct inode *ip;
>   	s64 xlen = 0;
>   	int bmask = 0, xsize;
>   	s64 xaddr;

      reply	other threads:[~2023-08-29 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 15:02 Colin Ian King
2023-08-29 17:21 ` 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=6974c489-3238-4037-81e5-3d9ec5e48ee0@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=brauner@kernel.org \
    --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®