From: Jean Delvare <khali@linux-fr.org>
To: "Ray Copeland" <ray.copeland@aprius.com>
Cc: <linux-kernel@vger.kernel.org>, <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 1/2] Wrong ADT7462_VOLT_COUNT for linux-2.6.30 adt7462 hwmon driver
Date: Thu, 17 Dec 2009 17:14:45 +0100 [thread overview]
Message-ID: <20091217171445.0bd28259@hyperion.delvare> (raw)
In-Reply-To: <AFEAE911EE22F64BACAB05ED86B4D4FC018DA328@EXVBE012-13.exch012.intermedia.net>
Hi Ray,
On Wed, 16 Dec 2009 17:26:19 -0800, Ray Copeland wrote:
> From: Ray Copeland <ray.copeland@aprius.com>
> Date: Wed, 16 Dec 2009
> Subject: [PATCH 1/2] Wrong ADT7462_VOLT_COUNT for linux-2.6.30 adt7462 hwmon driver
>
> Description:
>
> The #define ADT7462_VOLT_COUNT is wrong, it should be 13 not 12. All the
> for loops that use this as a limit count are of the typical form, "for
> (n = 0; n < ADT7462_VOLT_COUNT; n++)", so to loop through all voltages
> w/o missing the last one it is necessary for the count to be one greater
> than it is. (Specifically, you will miss the +1.5V 3GPIO input with count
> = 12 vs. 13.)
>
> Signed-off-by: Ray Copeland <ray.copeland@aprius.com>
>
> Diff with changes vs. original adt7462.c 2.6.30 version:
>
> --- adt7462.c.orig 2009-12-15 15:51:05.000000000 -0800
> +++ adt7462.c.volt_count 2009-12-16 14:06:01.000000000 -0800
> @@ -182,7 +182,7 @@
> *
> * Some, but not all, of these voltages have low/high limits.
> */
> -#define ADT7462_VOLT_COUNT 12
> +#define ADT7462_VOLT_COUNT 13
>
> #define ADT7462_VENDOR 0x41
> #define ADT7462_DEVICE 0x62
While the patch looks functionally correct, it is horribly broken in
its format. You sent a HTML mail instead of only plain text. Your
mailer turned the tabs into spaces. And the paths are missing from the
patch header.
Please learn how to send proper patches that kernel maintainers can
apply. Documentation/SubmittingPatches is a good start.
--
Jean Delvare
next prev parent reply other threads:[~2009-12-17 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AFEAE911EE22F64BACAB05ED86B4D4FC018DA312@EXVBE012-13.exch012.intermedia.net>
[not found] ` <AFEAE911EE22F64BACAB05ED86B4D4FC018DA31A@EXVBE012-13.exch012.intermedia.net>
2009-12-16 19:23 ` [PATCH 1/2] Wrong ADT7462_VOLT_COUNT for linux-2.6.30 adt7462 hwmon driver Darrick J. Wong
[not found] ` <AFEAE911EE22F64BACAB05ED86B4D4FC018DA328@EXVBE012-13.exch012.intermedia.net>
2009-12-17 16:14 ` Jean Delvare [this message]
2009-12-17 17:37 ` [lm-sensors] " Ray Copeland
2010-01-12 10:28 ` Jean Delvare
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=20091217171445.0bd28259@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=ray.copeland@aprius.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