linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: srinivas pandruvada <srinivas.pandruvada@intel.com>,
	linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH 0/8] HID-Sensor: v2
Date: Thu, 14 Jun 2012 14:39:37 +0100	[thread overview]
Message-ID: <4FD9E999.4010103@cam.ac.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1206141516350.8644@pobox.suse.cz>

On 6/14/2012 2:25 PM, Jiri Kosina wrote:
> On Thu, 14 Jun 2012, Jonathan Cameron wrote:
>
>>> As this is however a staging driver (and depends on IIO, which is a
>>> staging infrastructure), I suggest you resend the patch to staging
>>> maintainers so that it gets applied and we can work on polishing the
>>> driver there.
>>
>>> Also, what are the plans regarding moving IIO out of staging, please?
>> The core is out of staging as of the current cycle.
>
> Ah, you are right, I missed that this has already happened.
>
>> Drivers are moving out whenever someone has time to take a look at each
>> one and clean up any loose ends.  A couple went with the last merge
>> window, lots more a queued up for the next one.
>>
>> Generally any new drivers shouldn't go into staging but directly
>> into drivers/iio.
>
> For hid sensors I'd probably prefer drivers/hid though.
There's some pretty strong moves to clasify drivers by function not
by 'bus' (which is kind of what hid is I guess?)

I do wonder if this driver would work better as an mfd type device
with the sensor specific bits each having their own module?

Honestly I've never been much of a stickler for where things are as
long as someone is happy to look after them.
>
>> Sorry for my lack of responses on this revised version, been a busy
>> week and it's a fairly big review to do.
>
> Thanks,
>

  reply	other threads:[~2012-06-14 13:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10  1:53 [PATCH 0/8] HID-Sensor: v2 srinivas pandruvada
2012-06-10  1:53 ` [PATCH 1/8] HID-Sensors: Add ST Micro Sensor hub srinivas pandruvada
2012-06-10  1:53 ` [PATCH 2/8] HID-Sensors: Add Intel HID sensor srinivas pandruvada
2012-06-10  1:53 ` [PATCH 3/8] HID-Sensors: Sensor framework srinivas pandruvada
2012-06-10  1:53 ` [PATCH 4/8] HID-Sensors: Common attributes and interfaces srinivas pandruvada
2012-06-10  1:53 ` [PATCH 5/8] HID-Sensors: Added accelerometer 3D srinivas pandruvada
2012-06-10  1:53 ` [PATCH 6/8] HID-Sensors: Added Gyro 3D srinivas pandruvada
2012-06-10  1:53 ` [PATCH 7/8] HID-Sensors: Added Compass 3D srinivas pandruvada
2012-06-10  1:53 ` [PATCH 8/8] HID-Sensors: Added ALS srinivas pandruvada
2012-06-14 13:08 ` [PATCH 0/8] HID-Sensor: v2 Jiri Kosina
2012-06-14 13:12   ` Jonathan Cameron
2012-06-14 13:25     ` Jiri Kosina
2012-06-14 13:39       ` Jonathan Cameron [this message]
2012-06-14 15:25         ` Pandruvada, Srinivas
2012-06-14 16:04           ` Jonathan Cameron
2012-06-15 12:50           ` Jonathan Cameron
2012-06-15 15:27             ` Pandruvada, Srinivas
2012-06-15 13:12 ` Jonathan Cameron
2012-06-15 15:31   ` Pandruvada, Srinivas
2012-06-18  7:43     ` 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=4FD9E999.4010103@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=jkosina@suse.cz \
    --cc=linux-iio@vger.kernel.org \
    --cc=srinivas.pandruvada@intel.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;
as well as URLs for NNTP newsgroup(s).