From: Jonathan Cameron <jic23@cam.ac.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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: Thu, 12 Apr 2012 07:25:57 +0100 [thread overview]
Message-ID: <2607388f-9d57-4f55-9d7e-9788432ad551@email.android.com> (raw)
In-Reply-To: <20120411234632.GA11113@kroah.com>
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>On Wed, Apr 11, 2012 at 05:30:47PM +0100, Jonathan Cameron wrote:
>> >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.
>>
>> There are corners of the userspace abi that aren't but they aren't
>> related to the core so we can break the abi docs in two and just move
>> the good stuff...
>
>Ok, that sounds like a good first step.
>
>> >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.
>>
>> Will clear current queue under review then that would be great.
>>
>> Note we will need to leave a lot of drivers in staging for now so
>move
>> may require a few sed scripts to link up headers etc... quite a lot
>> of drivers are way off.
>
>Why would some drivers stay? It should only be because of the
>userspace
>api, not because they don't work properly, that's never stopped drivers
>from entering the main part of the kernel before :)
>
You got it in one. They have userspace interfaces that are miles from where they should be...
>> Lets start a fresh thread on the move to make sure everyone agrees on
>> what is ready!
>
>Sounds good.
>
>greg k-h
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2012-04-12 6:26 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
2012-04-11 16:30 ` Jonathan Cameron
2012-04-11 23:46 ` Greg Kroah-Hartman
2012-04-12 6:25 ` Jonathan Cameron [this message]
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=2607388f-9d57-4f55-9d7e-9788432ad551@email.android.com \
--to=jic23@cam.ac.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®