From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: Chris Verges <chrisv@cyberswitching.com>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] adxl345 accelerometer hwmon driver
Date: Thu, 02 Jul 2009 13:55:39 +0000 [thread overview]
Message-ID: <4A4CBC5B.6040103@cam.ac.uk> (raw)
In-Reply-To: <20090702132520.2e02959e@hyperion.delvare>
Jean Delvare wrote:
> Hi Chris,
>
> On Wed, 1 Jul 2009 13:52:28 -0700, Chris Verges wrote:
>>> Probably it's about time to put an end to this and kick all
>>> accelerometer drivers out of drivers/hwmon.
>> Hi Jean,
>>
>> This actually makes a lot of sense. The remaining question is,
>> "To where do we kick them?"
>>
>> After reading Jonathan's iio.pdf, I'm all on-board with the
>> adxl345 driver being placed in this new subsystem. However,
>> IIO subsystem isn't released into the "vanilla" kernel yet.
>>
>> Until the IIO subsystem is finished and I can port the driver
>> into it, what's the appropriate place for the adxl345 to
>> reside? misc? A new directory?
>
> This is a very valid question, and the current situation probably is
> the result of it not having a simple answer.
>
> We could create drivers/accelerometer and move the drivers there for
> the time being. Or we can move them to drivers/misc until iio is
> merged. Honestly, it would be great if iio could be finally merged, it
> would help driver authors get their driver in good shape and in the
> right place right away. But I know Jonathan is busy and I can't blame
> him if things take time.
Just for info, the latest version went to lkml about a minute ago. So now
it's over to other people finding the time to review / comment. (and me
to reply / implement their suggestions).
Thanks,
Jonathan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: Chris Verges <chrisv@cyberswitching.com>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [PATCH] adxl345 accelerometer hwmon driver
Date: Thu, 02 Jul 2009 13:55:39 +0000 [thread overview]
Message-ID: <4A4CBC5B.6040103@cam.ac.uk> (raw)
In-Reply-To: <20090702132520.2e02959e@hyperion.delvare>
Jean Delvare wrote:
> Hi Chris,
>
> On Wed, 1 Jul 2009 13:52:28 -0700, Chris Verges wrote:
>>> Probably it's about time to put an end to this and kick all
>>> accelerometer drivers out of drivers/hwmon.
>> Hi Jean,
>>
>> This actually makes a lot of sense. The remaining question is,
>> "To where do we kick them?"
>>
>> After reading Jonathan's iio.pdf, I'm all on-board with the
>> adxl345 driver being placed in this new subsystem. However,
>> IIO subsystem isn't released into the "vanilla" kernel yet.
>>
>> Until the IIO subsystem is finished and I can port the driver
>> into it, what's the appropriate place for the adxl345 to
>> reside? misc? A new directory?
>
> This is a very valid question, and the current situation probably is
> the result of it not having a simple answer.
>
> We could create drivers/accelerometer and move the drivers there for
> the time being. Or we can move them to drivers/misc until iio is
> merged. Honestly, it would be great if iio could be finally merged, it
> would help driver authors get their driver in good shape and in the
> right place right away. But I know Jonathan is busy and I can't blame
> him if things take time.
Just for info, the latest version went to lkml about a minute ago. So now
it's over to other people finding the time to review / comment. (and me
to reply / implement their suggestions).
Thanks,
Jonathan
next prev parent reply other threads:[~2009-07-02 13:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Acn6eDhBoTUmzVqOSVGG9a2LiwqVrA==>
2009-07-01 18:17 ` [lm-sensors] [PATCH] adxl345 accelerometer hwmon driver Chris Verges
2009-07-01 18:17 ` Chris Verges
2009-07-01 19:10 ` [lm-sensors] " Jonathan Cameron
2009-07-01 19:10 ` Jonathan Cameron
2009-07-01 19:19 ` Chris Verges
2009-07-01 19:19 ` Chris Verges
2009-07-01 20:13 ` Jean Delvare
2009-07-01 20:13 ` Jean Delvare
2009-07-01 20:52 ` [lm-sensors] " Chris Verges
2009-07-01 20:52 ` Chris Verges
2009-07-02 11:25 ` [lm-sensors] " Jean Delvare
2009-07-02 11:25 ` Jean Delvare
2009-07-02 13:55 ` Jonathan Cameron [this message]
2009-07-02 13:55 ` Jonathan Cameron
2009-07-02 8:04 ` [lm-sensors] " Éric Piel
2009-07-02 8:04 ` Éric Piel
2009-07-01 19:33 ` [lm-sensors] " Jean Delvare
2009-07-01 19:33 ` Jean Delvare
2009-07-02 14:15 ` Chris Verges
2009-07-02 17:38 ` Jonathan Cameron
2009-07-02 17:38 ` Jonathan Cameron
2009-07-02 17:43 ` Mike Frysinger
2009-07-02 17:43 ` Mike Frysinger
2009-07-02 17:59 ` Jonathan Cameron
2009-07-02 17:59 ` Jonathan Cameron
2009-07-02 18:12 ` Hennerich, Michael
2009-07-02 18:12 ` Hennerich, Michael
2009-07-02 18:15 ` Mike Frysinger
2009-07-02 18:15 ` Mike Frysinger
2009-07-02 17:59 ` Hennerich, Michael
2009-07-02 17:59 ` Hennerich, Michael
2009-08-14 11:05 ` XingChao Wang
2009-08-14 11:05 ` XingChao Wang
2009-08-14 13:48 ` [lm-sensors] " Chris Verges
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=4A4CBC5B.6040103@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=chrisv@cyberswitching.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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.