Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Zeng Heng <zengheng4@huawei.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org, liwei391@huawei.com
Subject: Re: [PATCH -next] hwmon: (nct6683) remove unused variable in nct6683_create_attr_group
Date: Sun, 2 Oct 2022 08:01:45 -0700	[thread overview]
Message-ID: <20221002150145.GA2895775@roeck-us.net> (raw)
In-Reply-To: <20220927114352.2498079-1-zengheng4@huawei.com>

On Tue, Sep 27, 2022 at 07:43:52PM +0800, Zeng Heng wrote:
> When enable 'unused-but-set-variable' compile
> warning option, it would raise warning as below:
> 
> drivers/hwmon/nct6683.c:415:9:
> warning: variable 'j' set but not used [-Wunused-but-set-variable]
> 
> Variable 'j' in nct6683_create_attr_group is unused,
> so remove it and simplify the 'for' loop.
> 
> Signed-off-by: Zeng Heng <zengheng4@huawei.com>

Applied.

Thanks,
Guenter

> ---
>  drivers/hwmon/nct6683.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
> index 6a9f420e7d32..a872f783e9cc 100644
> --- a/drivers/hwmon/nct6683.c
> +++ b/drivers/hwmon/nct6683.c
> @@ -412,7 +412,7 @@ nct6683_create_attr_group(struct device *dev,
>  	struct sensor_device_attr_u *su;
>  	struct attribute_group *group;
>  	struct attribute **attrs;
> -	int i, j, count;
> +	int i, count;
>  
>  	if (repeat <= 0)
>  		return ERR_PTR(-EINVAL);
> @@ -443,7 +443,7 @@ nct6683_create_attr_group(struct device *dev,
>  
>  	for (i = 0; i < repeat; i++) {
>  		t = tg->templates;
> -		for (j = 0; *t != NULL; j++) {
> +		while (*t) {
>  			snprintf(su->name, sizeof(su->name),
>  				 (*t)->dev_attr.attr.name, tg->base + i);
>  			if ((*t)->s2) {

      reply	other threads:[~2022-10-02 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 11:43 [PATCH -next] hwmon: (nct6683) remove unused variable in nct6683_create_attr_group Zeng Heng
2022-10-02 15:01 ` Guenter Roeck [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=20221002150145.GA2895775@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=liwei391@huawei.com \
    --cc=zengheng4@huawei.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