linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	linux-iio@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: Future plan for going out of staging
Date: Thu, 01 Dec 2011 20:46:53 +0000	[thread overview]
Message-ID: <4ED7E7BD.5060003@kernel.org> (raw)
In-Reply-To: <4ED4D7FA.60602@free-electrons.com>

On 11/29/2011 01:02 PM, Maxime Ripard wrote:
> Hi Jonathan,
> 
> As I am working on the hardware triggers part of the AT91 ADC driver,
> I'm wondering what is the plan for the second part of moving iio out of
> staging.
Right now I'm waiting for a quiet moment to push through large namespace
movements for the staging tree so that we can get the version not in
staging after staging-next in linux-next.  There's too much churn in
the staging tree to make it feasible any other way that I can think of.
> 
> Obviously, you will wait for the first patchset to get included, but
> what are you planning to move next ?
Plan is to move buffers next.  The sticking point is getting time to
finish writing the stuff to allow push in kernel users.  I have a
version that works, but haven't had a chance to clean it up.
> 
> I don't find the mail, but I recall you telling that the next batch will
> probably move triggers and buffers (or at least only kfifo), do I recall
> correctly ?
Yup.  ring_sw is a dodgy bit of code I wrote a long time ago and have
never been happy with so unless someone else works on it, I'm inclined
to leave that behind!
> 
> Also, do you have some kind of estimate on when we could begin to have
> the next patchset ?

I'm running very low on time at the moment due to family bits and job
getting in the way so can't really commit to a date I'm afraid.

I'm very much open to anyone else offering to take over some of the move
out of staging. Mostly it's just cut and paste stuff with the odd name
change.  Still the recent buffer cleanups need to go in first and a
couple more bits in my tree. I'll post those as a work in progress
shortly.

Jonathan
> 
> Thanks,
> Maxime
> 

      reply	other threads:[~2011-12-01 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 13:02 Future plan for going out of staging Maxime Ripard
2011-12-01 20:46 ` Jonathan Cameron [this message]

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=4ED7E7BD.5060003@kernel.org \
    --to=jic23@kernel.org \
    --cc=jic23@cam.ac.uk \
    --cc=linux-iio@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=thomas.petazzoni@free-electrons.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).