From: jim.cromie@gmail.com (Jim Cromie)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] #2073: VT1211 Driver review + docs
Date: Tue, 27 Jun 2006 16:41:20 +0000 [thread overview]
Message-ID: <44A15FB0.5010003@gmail.com> (raw)
In-Reply-To: <191fb4ca0606270754x29ac79ak194b509f9c9aac88@mail.gmail.com>
Juerg Haefliger wrote:
> Rudolf,
>
> I know you're busy but is there a chance that someone gives the vt1211
> a final review and merge it into main line soon? It's been around for
> a while now.
> Is there anything I can do to help?
>
> Thanks
> ...juerg
>
>
> On 6/4/06, lm-sensors <lm-sensors-notify at lm-sensors.org> wrote:
>
>> #2073: VT1211 Driver review + docs
>> --------------------+-------------------------------------------------------
>> Reporter: ruik | Owner: ruik
>> Type: task | Status: new
>> Priority: major | Milestone:
>> Component: kernel | Version:
>> Keywords: |
>> --------------------+-------------------------------------------------------
>> [http://lists.lm-sensors.org/pipermail/lm-sensors/2006-June/016329.html
>> VT1211 driver review]
>>
>>
your patch passes the leading, trailing whitespace tests (which you know):
cat -TE attachment-0001.obj | grep '^+ ' |more
cat -TE attachment-0001.obj | grep ' $' |more
2 trivial notes:
+ default:
+ printk(KERN_ERR DRVNAME ": Unknown attr fetch\n");
since these are in your callbacks, which have a struct device *dev,
you could change them to
dev_err(dev, "Unknown attr.....
+ }
Also, just below here:
+ /* pwm & temp auto point registers */
+ data->pwm_auto_pwm[0][0] = 255; /* hard wired */
+ data->pwm_auto_pwm[0][1] = vt1211_read8(data,
you could have done those initializations in a loop.
Im assuming this would shrink the object by a teeny amount.
And one 'idle-curiosity' question:
what happens when you rmmod then modprobe ? any surprises ?
next prev parent reply other threads:[~2006-06-27 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 14:54 [lm-sensors] #2073: VT1211 Driver review + docs Juerg Haefliger
2006-06-27 16:41 ` Jim Cromie [this message]
2006-06-27 17:48 ` Juerg Haefliger
2006-06-30 8:56 ` Rudolf Marek
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=44A15FB0.5010003@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.