From: Jean Delvare <khali@linux-fr.org>
To: "Chris Verges" <chrisv@cyberswitching.com>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
"Rob Owings" <rowings@thermistor.com>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
lm-sensors@lm-sensors.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] linux-2.6.32-directemp
Date: Sat, 6 Feb 2010 19:01:17 +0100 [thread overview]
Message-ID: <20100206190117.6fc3be63@hyperion.delvare> (raw)
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C2445C2@mail03.cyberswitching.local>
On Sat, 6 Feb 2010 08:58:14 -0800, Chris Verges wrote:
> > Wouldn't it make sense to make use of hardware monitoring interfaces so
> > lm_sensors could handle the sensor information? (added to CC)
> >
> > This would also be a good reason to have the driver on kernel side
> > rather than somewhere in userspace.
>
> Hi Bruno,
>
> I agree. However, I've had other drivers in the past been pooh-pooh'd by the lm-sensors maintainers because they don't seem to fit exactly what the lm-sensors folks want in a driver. Unfortunately, I seem to be bad at understanding the purpose of lm-sensors. :-) I'd like to get their approval before any work is done to migrate over to lm-sensors.
I can see that you tried to submit a driver for an accelerometer chip.
This indeed did not quite fit in the hwmon subsystem (although for
historical and unfortunate reasons we have a couple of them sitting
there at the moment... they should really go away!)
Temperature sensors definitely fit in the hwmon subsystem.
Humidity sensors... why not, we have already one.
--
Jean Delvare
prev parent reply other threads:[~2010-02-06 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 4:47 [PATCH] linux-2.6.32-directemp Chris Verges
2010-02-05 15:45 ` Alan Stern
2010-02-05 17:16 ` Greg KH
2010-02-05 17:32 ` Chris Verges
2010-02-05 20:40 ` Andrew Morton
2010-02-05 21:32 ` Chris Verges
2010-02-05 21:46 ` Andrew Morton
2010-02-05 23:58 ` Greg KH
2010-02-06 0:26 ` Chris Verges
2010-02-06 8:55 ` Greg KH
2010-02-06 9:42 ` Bruno Prémont
[not found] ` <68FBE0F3CE97264395875AC1C468F22C2445C2@mail03.cyberswitching.local>
2010-02-06 18:01 ` Jean Delvare [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=20100206190117.6fc3be63@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=bonbons@linux-vserver.org \
--cc=chrisv@cyberswitching.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rowings@thermistor.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