From: jim.cromie@gmail.com (Jim Cromie)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] vt1211 driver (was hwmon/pc87360 as a platform
Date: Mon, 17 Apr 2006 16:04:06 +0000 [thread overview]
Message-ID: <4443BC76.3060905@gmail.com> (raw)
Juerg Haefliger wrote:
>> The SHOW_SET_*_* constants are just a bit off-putting at first read,
>> but I know what you mean, and I dont have a better idea.
>> maybe SHOW_SETTNG_*_* ?
>> or SHOW_CURR_*_*, thats confuse-able with the current reading
>>
>
> Well SHOW_SET_xxx_yyy is supposed to hint that the constant is used in
> both the show_xxx and set_xxx callbacks. It's the best I could come up
> with although I have to admit I didn't spend too much time thinking
> about this....
>
>
>> you can improve your printks :
>>
>> s/(printk\(KERN_DEBUG)/dev_dbg\(&pdev->dev/;
>> s/(printk\(KERN_ERR)/dev_err\(&pdev->dev/
>> s/(printk\(KERN_INFO)/dev_info\(&pdev->dev/
>>
>> at least where pdev has already been initd
>>
>
> Hmm... I thought I used printks only in places where pdev is not initialized.
>
>
I didnt look that carefully.
>> Ill try to read thru the enire patch this weekend sometime.
>>
>
> I certainly appreciate the review :-)
>
>
good thing that *this* is so flexible ;-)
> ...juerg
>
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hwmon-vt1211-driver-review
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060417/2985cd2c/hwmon-vt1211-driver-review.pl
next reply other threads:[~2006-04-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 16:04 Jim Cromie [this message]
2006-04-17 17:46 ` [lm-sensors] vt1211 driver (was hwmon/pc87360 as a platform Juerg Haefliger
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=4443BC76.3060905@gmail.com \
--to=jim.cromie@gmail.com \
--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.