From: Jean Delvare <khali@linux-fr.org>
To: "Éric Piel" <Eric.Piel@tremplin-utc.net>
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Yan Burman <burman.yan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
HWMON <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH 2.6.25.4] hwmon: HP Mobile Data Protection System 3D ACPI driver -- please review!
Date: Thu, 5 Jun 2008 08:29:50 +0200 [thread overview]
Message-ID: <20080605082950.6957f1a2@hyperion.delvare> (raw)
In-Reply-To: <484728B2.1000209@tremplin-utc.net>
On Thu, 05 Jun 2008 01:43:46 +0200, Éric Piel wrote:
> 05-06-08 01:05, Pavel Machek wrote/a écrit:
> >> So my advice is that you don't wait for a review from the hwmon people,
> >> because apparently we don't have much interest in this type of device,
> >> so you'll be waiting forever. You're much better adding the mdps driver
> >> to drivers/misc through Andrew Morton, at least until someone takes
> >> care of creating a subsystem for this type of devices and move all
> >> existing drivers there.
> >
> > Just create drivers/accel ... accelerometers are quite common these
> > days. Going to drivers/misc is okay, too, I guess -- moves are easy
> > with git ;-).
>
> Yes, why not do one little step to the correct direction now and create
> drivers/accel, it will likely be the chosen name anyway! That will not
> yet be a "real" subsystem, just a place to put all the related drivers
> already present together.
Well, I would expect all these accelerometer drivers to have a common,
standardized interface, so this should most probably become a real
subsystem in the long run.
> Anyone against this idea?
I am in favor of it.
--
Jean Delvare
next prev parent reply other threads:[~2008-06-05 6:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 12:05 [PATCH 2.6.25.4] hwmon: HP Mobile Data Protection System 3D ACPI driver Yan Burman
2008-06-04 19:24 ` [PATCH 2.6.25.4] hwmon: HP Mobile Data Protection System 3D ACPI driver -- please review! Éric Piel
2008-06-04 20:58 ` Jean Delvare
2008-06-04 22:57 ` Éric Piel
2008-06-05 6:27 ` Jean Delvare
2008-06-04 23:05 ` Pavel Machek
2008-06-04 23:43 ` Éric Piel
2008-06-05 6:29 ` Jean Delvare [this message]
2008-06-05 9:38 ` [lm-sensors] " Jonathan Cameron
2008-06-05 20:34 ` Éric Piel
2008-06-05 22:27 ` Pau Oliva Fora
2008-06-06 14:24 ` Dmitry Torokhov
2008-06-06 15:29 ` Pau Oliva Fora
2008-06-06 14:56 ` Eric Piel
2008-06-06 15:30 ` Pau Oliva Fora
2008-06-06 8:51 ` Jonathan Cameron
2008-06-04 23:03 ` Pavel Machek
2008-06-04 23:29 ` Éric Piel
2008-06-05 1:06 ` Henrique de Moraes Holschuh
2008-06-05 8:19 ` Pavel Machek
2008-06-06 14:27 ` Dmitry Torokhov
2008-06-06 14:59 ` Eric Piel
2008-06-06 15:11 ` Dmitry Torokhov
2008-06-06 15:37 ` Pau Oliva Fora
2008-06-05 5:17 ` [PATCH 2.6.25.4] hwmon: HP Mobile Data Protection System 3D ACPI driver Andrew Morton
2008-06-05 7:43 ` [lm-sensors] " Riku Voipio
2008-06-05 8:28 ` Eric Piel
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=20080605082950.6957f1a2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=Eric.Piel@tremplin-utc.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=burman.yan@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=pavel@suse.cz \
/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