On Wed, Apr 11, 2012 at 07:19:01AM +0100, Jonathan Cameron wrote: > > > Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > >On Tue, Apr 10, 2012 at 08:39:40PM +0100, Jonathan Cameron wrote: > > > >> 1) Review of code. This is crucial. If people have a little time > >> ripping holes in the core IIO code is what we need. Arnd did a good > >job > >> of this a while back. Others have done bits of it since. > > > >> 2) Getting the push code tidied up and pushed out. I'll post it as > >an > >> updated rfc to linux-iio shortly. All I had left that definitely > >> wanted doing here was cleaning up the example iio to input bridge > >> driver. That can happen later. > > > >For these two can we refactor in place? That's pretty much what seems > >to have been happening anyway... > > > I guess it comes down to whether Linus will pull. 2 should be there > within a week or so anyway depending mostly on analog testing I > haven't broken any of their drivers. Hm, shouldn't I be the one that moves this out of staging? :) Anyway, all I care about to get this code out of staging is that you feel your userspace api is "sane" and not going to change. Your in-kernel stuff can radically change every kernel release with no objection from me at all. And from what I can tell, your userspace stuff looks pretty stable now, right? So, I don't mind moving this all out of staging for 3.5 as-is. If so, I'll be glad to make the change to my repo so it starts to show up in linux-next in the "correct" place whenever you want me to. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
