From: Steven King <sfking@fdwdc.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jean Delvare <khali@linux-fr.org>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: driver for TI tmp102 temperature sensor
Date: Thu, 4 Feb 2010 13:17:37 -0800 [thread overview]
Message-ID: <201002041317.37574.sfking@fdwdc.com> (raw)
In-Reply-To: <20100204102203.ecf4bbb5.akpm@linux-foundation.org>
On Thursday 04 February 2010 10:22:03 Andrew Morton wrote:
> On Wed, 3 Feb 2010 17:23:49 -0800
>
> Steven King <sfking@fdwdc.com> wrote:
> > The TI TMP102 is similar to the lm75. It differs from the lm75 by having
> > a 16 bit conf register and the temp registers have a minimum resolution
> > of 12bits; the extended conf register can select 13 bit resolution (which
> > this driver does) and also change the update rate (which this driver
> > currently doesn't use).
>
> A neat little driver.
Thanks.
> checkpatch spits this warning:
>
> WARNING: struct dev_pm_ops should normally be const
> #387: FILE: drivers/hwmon/tmp102.c:300:
> +static struct dev_pm_ops tmp102_dev_pm_ops = {
>
> which seems truthful enough.
Indeed. I am, however, somewhat surprised since I ran the patch thru
checkpatch before posting it and no errors or warnings were reported. Is
there a version of checkpatch other than the one included in the tree that I
should be using?
>
> And doing this will hurt readers' brains less:
>
>
>
> Use conventional array-walk loop.
Ah yes, an idiosyncrasy of mine in preferring do while over for loops
especially when I 'know' the initial test will pass. Whatever is the
preferred idiom for the kernel is fine with me.
--
Steven King -- sfking at fdwdc dot com
next prev parent reply other threads:[~2010-02-04 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 1:23 Steven King
2010-02-04 18:22 ` Andrew Morton
2010-02-04 21:17 ` Steven King [this message]
2010-02-04 21:26 ` Andrew Morton
2010-02-04 18:37 ` Jean Delvare
2010-02-04 21:57 ` Steven King
2010-02-05 8:12 ` 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=201002041317.37574.sfking@fdwdc.com \
--to=sfking@fdwdc.com \
--cc=akpm@linux-foundation.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome