From: "Éric Piel" <Eric.Piel@tremplin-utc.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Guenter Roeck <guenter.roeck@ericsson.com>,
Andrew Morton <akpm@linux-foundation.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] [PATCH v2] lis3: Fix Oops with NULL platform data
Date: Fri, 24 Sep 2010 17:22:01 +0200 [thread overview]
Message-ID: <4C9CC219.4090304@tremplin-utc.net> (raw)
In-Reply-To: <20100924163005.7704f63e@endymion.delvare>
Op 24-09-10 16:30, Jean Delvare schreef:
> Well, as long as the driver lives in drivers/hwmon and the hwmon
> subsystem is maintained, it seems fair to consider the driver
> maintained.
>
> That being said, I indeed would like all non-hwmon drivers to go away
> from drivers/hwmon. Originally we were waiting for iio to settle first,
> but apparently this is taking forever. The 4 drivers I would like to
> kick are: ams, hdaps, lis3lv02d and applesmc. They are primarily
> accelerometer device drivers. Not sure where to put them,
> drivers/accel(erometer), drivers/misc, drivers/misc/accel(erometer),
> drivers/input/accel(erometer)... Opinions welcome.
As maintainer of the lis3lv02d driver, I'd completely support the move too.
IMHO, an accelerometer is just another input device (usually with 2 or 3
axes), so moving them to drivers/input/accel would make sense.
Eric
next prev parent reply other threads:[~2010-09-24 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 5:58 [PATCH v2] lis3: Fix Oops with NULL platform data Takashi Iwai
2010-09-24 13:58 ` Guenter Roeck
2010-09-24 14:14 ` Takashi Iwai
2010-09-24 14:30 ` [lm-sensors] " Jean Delvare
2010-09-24 15:10 ` Jonathan Cameron
2010-09-24 15:17 ` Guenter Roeck
2010-09-24 17:07 ` Jonathan Cameron
2010-09-25 11:11 ` Jean Delvare
2010-09-25 11:01 ` Jean Delvare
2010-09-25 13:47 ` Jonathan Cameron
2010-09-24 15:16 ` Guenter Roeck
2010-09-24 15:22 ` Éric Piel [this message]
2010-09-24 17:14 ` Jonathan Cameron
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=4C9CC219.4090304@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=guenter.roeck@ericsson.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=tiwai@suse.de \
/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