From: Jonathan Cameron <jic23@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-iio@vger.kernel.org, lm-sensors@lm-sensors.org, khali@linux-fr.org
Subject: Re: [PATCH] hwmon: Move the IIO client driver for hwmon out of staging
Date: Thu, 21 Mar 2013 07:16:49 +0000 [thread overview]
Message-ID: <514AB3E1.8070107@kernel.org> (raw)
In-Reply-To: <20130320234405.GA29172@roeck-us.net>
On 03/20/2013 11:44 PM, Guenter Roeck wrote:
> On Wed, Mar 20, 2013 at 10:21:19PM +0000, Jonathan Cameron wrote:
>> This driver uses channel maps, defined either through device tree
>> or platform data, to create a hwmon driver which acts as a client
>> for the underlying IIO device channels. Thus a general purpose
>> IIO adc driver can be used to provide hardware monitoring using a subset
>> of its channels.
>>
>> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
>> cc: Guenter Roeck <linux@roeck-us.net>
>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
>
>>
>> --
>> The only non move changes here concern the description and changes to the
>> dependencies to IIO explicit and hwmon implicit.
>>
>> I'm proposing moving this into hwmon on the basis of placing drivers
>> based on what they provide rather than what their underlying hardware
>> is.
>>
> That is what I would suggest as well.
>
> I assume you will take this through the iio tree, as it depends
> on my previous patch, correct ?
Yes. All moves from staging like this one (rather than rewrites) go through
GregKH's staging tree anyway so routing through IIO (which he pulls into there)
is definitely the way to go.
Jonathan
prev parent reply other threads:[~2013-03-21 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 22:21 [PATCH] hwmon: Move the IIO client driver for hwmon out of staging Jonathan Cameron
2013-03-20 23:44 ` Guenter Roeck
2013-03-21 7:16 ` Jonathan Cameron [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=514AB3E1.8070107@kernel.org \
--to=jic23@kernel.org \
--cc=khali@linux-fr.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox