From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v2 2/2] hwmon: (atxp1) Drop auto-detection
Date: Sun, 31 May 2015 15:31:08 +0000 [thread overview]
Message-ID: <556B293C.7080102@roeck-us.net> (raw)
In-Reply-To: <1432931265-21499-2-git-send-email-linux@roeck-us.net>
Hi Jean,
On 05/31/2015 06:09 AM, Jean Delvare wrote:
> On Sat, 30 May 2015 11:17:28 -0700, Guenter Roeck wrote:
>> On 05/29/2015 01:27 PM, Guenter Roeck wrote:
>>> Auto-detection for this chip is highly unreliable, and one of its
>>> I2C addresses can also be used by EEPROMs, increasing the risk for
>>> false positives even more. Drop auto-detection entirely to remove
>>> the risk.
>>>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>> ---
>>> v2: Add text describing the supported I2C addresses, and that the driver
>>> must be instantiated explicitly.
>>> Validate supported vrm values in probe function.
>>>
>> [ ... ]
>>
>>> -
>>> static int atxp1_probe(struct i2c_client *client,
>>> const struct i2c_device_id *id)
>>> {
>>> @@ -309,6 +269,11 @@ static int atxp1_probe(struct i2c_client *client,
>>>
>>> /* Get VRM */
>>> data->vrm = vid_which_vrm();
>>> + if (data->vrm != 90 && data->vrm != 91) {
>>> + dev_err(&adapter->dev, "atxp1: Not supporting VRM %d.%d\n",
>
> You have a stray space before "dev_err".
>
>>> + data->vrm / 10, data->vrm % 10);
>>
>> s/&adapter->//
>>
>> Compile testing is always a good idea.
>
> After fixing both issues:
>
> Reviewed-by: Jean Delvare <jdelvare@suse.de>
>
Fixed. Thanks a lot for the reviews!
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2015-05-31 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 20:27 [lm-sensors] [PATCH v2 2/2] hwmon: (atxp1) Drop auto-detection Guenter Roeck
2015-05-30 18:17 ` Guenter Roeck
2015-05-31 13:09 ` Jean Delvare
2015-05-31 15:31 ` 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=556B293C.7080102@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.