From: Mike Snitzer <snitzer@redhat.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: agk@redhat.com, dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: dm: remove unneeded variable 'sz'
Date: Tue, 9 Mar 2021 15:14:50 -0500 [thread overview]
Message-ID: <20210309201449.GB16277@redhat.com> (raw)
In-Reply-To: <1615282320-28246-1-git-send-email-yang.lee@linux.alibaba.com>
On Tue, Mar 09 2021 at 4:32am -0500,
Yang Li <yang.lee@linux.alibaba.com> wrote:
> Fix the following coccicheck warning:
> ./drivers/md/dm-ps-service-time.c:85:10-12: Unneeded variable: "sz".
> Return "0" on line 105
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
This type of change gets proposed regaularly. Would appreciate it if
you could fix coccicheck to not get this wrong. The local 'sz' variable
is used by the DMEMIT macro (as the earlier reply to this email informed
you).
Also, had you tried to compile the code with your patch applied you'd
have quickly realized your patch wasn't correct.
Mike
> ---
> drivers/md/dm-ps-service-time.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/md/dm-ps-service-time.c b/drivers/md/dm-ps-service-time.c
> index 9cfda66..12dd5ce 100644
> --- a/drivers/md/dm-ps-service-time.c
> +++ b/drivers/md/dm-ps-service-time.c
> @@ -82,7 +82,6 @@ static void st_destroy(struct path_selector *ps)
> static int st_status(struct path_selector *ps, struct dm_path *path,
> status_type_t type, char *result, unsigned maxlen)
> {
> - unsigned sz = 0;
> struct path_info *pi;
>
> if (!path)
> @@ -102,7 +101,7 @@ static int st_status(struct path_selector *ps, struct dm_path *path,
> }
> }
>
> - return sz;
> + return 0;
> }
>
> static int st_add_path(struct path_selector *ps, struct dm_path *path,
> --
> 1.8.3.1
>
prev parent reply other threads:[~2021-03-09 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 9:32 [PATCH] dm: remove unneeded variable 'sz' Yang Li
2021-03-09 13:38 ` kernel test robot
2021-03-09 17:24 ` kernel test robot
2021-03-09 20:14 ` Mike Snitzer [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=20210309201449.GB16277@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--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