public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	List Linux Kernel <linux-kernel@vger.kernel.org>
Subject: ALS subsystem (was Re: [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver)
Date: Wed, 25 Nov 2009 12:56:49 +0200	[thread overview]
Message-ID: <20091125105649.GJ16444@smtp.gmail.com> (raw)
In-Reply-To: <1257843493.4469.25.camel@rzhang-dt>

On 09 Nov 10, Zhang Rui wrote:
> On Tue, 2009-11-10 at 02:08 +0800, Jonathan Cameron wrote:
> > Amit Kucheria wrote:
> > > On 09 Nov 09, Jonathan Cameron wrote:
> > >> Hi Amit,
> > >>
> > >> Normally I'd welcome this in IIO, except that all ambient light sensors are in the
> > >> process of moving to the new ALS subsystem.  There are still some issues to resolve
> > >> in that subsystem (mainly to do with naming conventions) but hopefully we will
> > >> get them sorted out shortly.
> > > 
> > > Groan! :)
> > You have my sympathies on this! Typical that the first other developer to put
> > forward a patch for IIO picks the one type of device we are moving out.
> > If you do have any comments on IIO as a result of using it please send them
> > on.
> > > Who will be the subsystem maintainer and is there already a public git
> > > tree?
> > No git tree as far as I know.  Maintainer is Zhang Rui (Cc'd)
> > Zhang, what are your plans wrt to that?  I guess I can put one up with the current
> > patches if it is helpful?  We really need to sort out the naming issue as the one
> > thing that people have come out against. 
> > 
> well. I'd prefer a generic name alsX with an extra "name"/"desc" file.
> 
> > After that I'm guessing ping Andrew Morton to see if he is willing to handle the push
> > to Linus? Or does Zhang want to try doing one directly?
> > 
> I'll refresh the patch and send to Andrew.
>

Rui,

Is there any progress on this? I haven't seen a patch refresh on LKML. 

I can help if you need any.

Regards,
Amit


-- 
-------------------------------------------------------------------------
Amit Kucheria,				 Kernel Developer, Verdurent
-------------------------------------------------------------------------

  reply	other threads:[~2009-11-25 10:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 13:14 [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver Amit Kucheria
2009-11-09 13:14 ` [PATCH 2/2] omap: rx51: Enable RX-51 ambient light sensor Amit Kucheria
2009-11-09 13:57 ` [PATCH 1/2] staging: iio: tsl2563 ambient light sensor driver Jonathan Cameron
2009-11-09 14:03   ` Jonathan Cameron
2009-11-09 14:24   ` Amit Kucheria
2009-11-09 18:08     ` Jonathan Cameron
2009-11-10  8:58       ` Zhang Rui
2009-11-25 10:56         ` Amit Kucheria [this message]
2009-11-10  9:52       ` Amit Kucheria
2009-11-09 19:03 ` Jonathan Cameron
2009-11-19 20:04 ` patch staging-iio-tsl2563-ambient-light-sensor-driver.patch added to gregkh-2.6 tree gregkh

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=20091125105649.GJ16444@smtp.gmail.com \
    --to=amit.kucheria@verdurent.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@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