From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: IIO: rest of cycle todo list.
Date: Fri, 02 Sep 2011 17:31:21 +0100 [thread overview]
Message-ID: <4E6104D9.2090508@cam.ac.uk> (raw)
Hi All,
I've now sent everything that was in iio-blue.git master branch
on to Greg (note that not everything is on kernel.org yet for
obvious reasons but it has all been on list). So what is on
the todo list for the rest of this cycle?
1) More cleanups + make sure that in_ out_ prefix stuff propagates
down into the drivers (only done for chan_spec stuff so far).
2) Documentation updates / rewrite for out of staging.
3) Review / improvement of the outofstaging tree. I'd like to post
it widely fairly soon so please can anyone with any spare time take
a look - suggest and add more drivers to the example set.
Just thought I'd keep people up to date with where things are as
the absence of hera means development is not as open as normal!
Jonathan
reply other threads:[~2011-09-02 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E6104D9.2090508@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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 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).