From: Guenter Roeck <linux@roeck-us.net>
To: Amy.Shih@advantech.com.tw, she90122@gmail.com
Cc: oakley.ding@advantech.com.tw, bichan.lu@advantech.com.tw,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v1,1/1] hwmon: (nct7904) Fix the incorrect value of vsen_mask in nct7904_data struct.
Date: Sun, 15 Sep 2019 19:57:19 -0700 [thread overview]
Message-ID: <4bfa5c0e-e6c9-b47c-3b22-5ce9786bc0fd@roeck-us.net> (raw)
In-Reply-To: <20190916021836.1945-1-Amy.Shih@advantech.com.tw>
On 9/15/19 7:18 PM, Amy.Shih@advantech.com.tw wrote:
> From: "amy.shih" <amy.shih@advantech.com.tw>
>
> Voltage sensors overlap with external temperature sensors. Detect
> the multi-function of voltage, thermal diode and thermistor from
> register VT_ADC_MD_REG to set value of vsen_mask in nct7904_data
> struct.
>
> Signed-off-by: amy.shih <amy.shih@advantech.com.tw>
> ---
> drivers/hwmon/nct7904.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/nct7904.c b/drivers/hwmon/nct7904.c
> index 95b447cfa24c..ad61c3d92411 100644
> --- a/drivers/hwmon/nct7904.c
> +++ b/drivers/hwmon/nct7904.c
> @@ -919,8 +919,11 @@ static int nct7904_probe(struct i2c_client *client,
> bit = (1 << i);
> if (val == 0)
> data->tcpu_mask &= ~bit;
> - else if (val == 0x1 || val == 0x2)
> + else if (val == 0x1 || val == 0x2) {
> data->temp_mode |= bit;
> + data->vsen_mask &= ~(0x06 << (i * 2));
> + } else
> + data->vsen_mask &= ~(0x06 << (i * 2));
The second instruction is the same for both branches of the if()
statement and can thus be moved outside.
Either case, if {} is needed for one branch of an if statement,
it needs to be used for the other branch(es) as well.
Guenter
prev parent reply other threads:[~2019-09-16 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 2:18 Amy.Shih
2019-09-16 2:57 ` 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=4bfa5c0e-e6c9-b47c-3b22-5ce9786bc0fd@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Amy.Shih@advantech.com.tw \
--cc=bichan.lu@advantech.com.tw \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oakley.ding@advantech.com.tw \
--cc=she90122@gmail.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
all inboxes | Powered by JetHome®