From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
mingo@elte.hu, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management
Date: Wed, 11 Apr 2012 08:38:11 -0700 [thread overview]
Message-ID: <20120411153811.GA28101@kroah.com> (raw)
In-Reply-To: <e65fbfb8-1169-46dc-aad9-1dc9dbb91e8f@email.android.com>
On Wed, Apr 11, 2012 at 07:19:01AM +0100, Jonathan Cameron wrote:
>
>
> Mark Brown <broonie@opensource.wolfsonmicro.com> 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
next prev parent reply other threads:[~2012-04-11 15:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 13:20 Alan Cox
2012-04-10 13:12 ` Mark Brown
2012-04-10 13:25 ` Alan Cox
2012-04-10 13:33 ` Mark Brown
2012-04-10 13:42 ` Alan Cox
2012-04-10 14:07 ` Mark Brown
2012-04-10 14:15 ` Alan Cox
2012-04-10 15:19 ` Mark Brown
2012-04-10 16:56 ` Alan Cox
2012-04-10 17:58 ` Mark Brown
2012-04-10 19:39 ` Jonathan Cameron
2012-04-10 22:37 ` Mark Brown
2012-04-11 6:19 ` Jonathan Cameron
2012-04-11 7:44 ` Jonathan Cameron
2012-04-11 15:38 ` Greg Kroah-Hartman [this message]
2012-04-11 16:30 ` Jonathan Cameron
2012-04-11 23:46 ` Greg Kroah-Hartman
2012-04-12 6:25 ` Jonathan Cameron
2012-04-11 10:24 ` Alan Cox
2012-04-11 10:38 ` Mark Brown
2012-04-11 10:48 ` Jonathan Cameron
2012-04-11 11:13 ` Alan Cox
2012-04-11 11:19 ` Jonathan Cameron
2012-04-11 12:30 ` Alan Cox
2012-04-11 12:55 ` Jonathan Cameron
2012-04-12 17:53 ` Mark Brown
2012-04-12 18:04 ` Mark Brown
2012-04-11 11:38 ` Jonathan Cameron
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=20120411153811.GA28101@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome