All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Kristina Martšenko" <kristina.martsenko@gmail.com>,
	linux-iio@vger.kernel.org
Subject: IIO drivers left in drivers/staging/
Date: Tue, 10 Jun 2014 18:30:07 -0700	[thread overview]
Message-ID: <20140611013007.GA32756@kroah.com> (raw)

Hi Jonathan,

I'd really like to figure out what is left to do with all of the
remaining IIO staging drivers, and see if we can get them all moved out
soon.

As part of the OPW intern program, Kristina has agreed to help out with
staging kernel drivers and I thought that doing this type of work would
be a great task.  There seems to be a number of different types of
IIO drivers here, so that should keep her from being bored with just one
specific type of sensor.  There are also some "dummy" IIO drivers, which
I don't really understand what they are for (as well as why they remain
in staging.)

The drivers/staging/TODO file seems pretty old, being dated back in 2009
and not really done much with the exception of adding one entry.

So, any thoughts about what to do here?  Any pointers to devices that
she can aquire if that needs to happen, or APIs that need to be
standardized across types?

thanks,

greg k-h

             reply	other threads:[~2014-06-11  1:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  1:30 Greg KH [this message]
2014-06-11  6:37 ` IIO drivers left in drivers/staging/ Jonathan Cameron
2014-06-11  8:05 ` Jonathan Cameron
2014-06-12 11:21   ` Kristina Martšenko
2014-06-18 12:43     ` Kristina Martšenko
2014-06-18 12:56       ` Peter Meerwald
2014-06-18 16:33         ` Jonathan Cameron
2014-06-18 17:47         ` Greg KH
2014-06-18 18:06           ` Jonathan Cameron
2014-06-18 19:45             ` Jonathan Cameron
2014-06-19 12:54           ` Alexandre Belloni
2014-06-20 20:42             ` Greg KH
2014-06-21  7:55               ` Alexandre Belloni
2014-06-21 20:18                 ` Greg KH

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=20140611013007.GA32756@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=kristina.martsenko@gmail.com \
    --cc=linux-iio@vger.kernel.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.