From: Jonathan Cameron <jic23@kernel.org>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: IIO merge probably closed for 3.7 cycle.
Date: Mon, 24 Sep 2012 09:10:34 +0100 [thread overview]
Message-ID: <5060157A.805@kernel.org> (raw)
Linus has definitively stated that he won't do another release candidate
for 3.6, but his rc7 email implied it was unlikely.
Anyhow, that means that I'll be queuing any new stuff up
for the 3.8 cycle from now on. (Given we route through GregKH
we have to obey his one week limit + I agree entirely with his
policy on this so would apply such a limit anyway)
Personally I'll be having another go at the multiple buffered
support patches over the next week or so and really really hope
I can finally get those merged. For the interested the current
version (which is more or less ready for posting is in the wip
branch of iio.git on kernel.org.
I'd also hope that the 3.8 cycle carries on the process of
moving individual drivers out of staging and given
I haven't actually moved any of my own yet I will be
spending some time doing that.
There have been some nice new drivers and also a lot of good cleanup
work on the exiting code. Nice to see has been the number of new
contributors to the subsystem and in particular that more and more
people have been willing to get their hands dirty in the core code :)
I won't name any names as I'll just forget someone and the git
log will do the job nicely for me!
Anyhow, looking forward to a productive 3.8 cycle, in particular
merging the various drivers currently mid way through the review
process.
Jonathan
reply other threads:[~2012-09-24 8:10 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=5060157A.805@kernel.org \
--to=jic23@kernel.org \
--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.