linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Future plan for going out of staging
@ 2011-11-29 13:02 Maxime Ripard
  2011-12-01 20:46 ` Jonathan Cameron
  0 siblings, 1 reply; 2+ messages in thread
From: Maxime Ripard @ 2011-11-29 13:02 UTC (permalink / raw)
  To: Jonathan Cameron; +Cc: linux-iio, Nicolas Ferre, Thomas Petazzoni

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.

Obviously, you will wait for the first patchset to get included, but
what are you planning to move next ?

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 ?

Also, do you have some kind of estimate on when we could begin to have
the next patchset ?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Future plan for going out of staging
  2011-11-29 13:02 Future plan for going out of staging Maxime Ripard
@ 2011-12-01 20:46 ` Jonathan Cameron
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Cameron @ 2011-12-01 20:46 UTC (permalink / raw)
  To: Maxime Ripard
  Cc: Jonathan Cameron, linux-iio, Nicolas Ferre, Thomas Petazzoni

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
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-12-01 20:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-29 13:02 Future plan for going out of staging Maxime Ripard
2011-12-01 20:46 ` Jonathan Cameron

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).