Re: OMAP34xx

Austin, Brian
2012-02-09T01:43:12Z

On Feb 8, 2012, at 6:47 PM, "Greg KH" <gregkh@linuxfoundation.org> wrote:

> On Wed, Feb 08, 2012 at 05:14:18PM -0700, Paul Walmsley wrote:
>> Hi Greg
>>
>> was just directed at this thread:
>>
>> On Wed, 8 Feb 2012, Greg KH wrote:
>>
>>> Don't send me anything, saying it needs to get into the -rc merge
>>> window, that you don't actually want to see merged. Otherwise, how long
>>> am I supposed to know to wait? That's just looney.
>>
>> We did want to see it merged. But then we came up with a better fix,
>> which is why I asked you to revert the original in favor of the new
>> version:
>>
>> http://marc.info/?l=linux-arm-kernel&m=132760582332651&w=2
>>
>> If we'd realized that the second version would be delayed until 3.4, we
>> wouldn't have wanted the first version to be reverted :-(
>
> You said the first version was broken.
>
> Anyway, moving on...
>
>>>> The version you have currently queued is needed for v3.3 as they fix
>>>> brokenness on v3.3. Any chance they can be applied queued for 3.3?
>>>> We'll have another set of enhancements on top of those that are
>>>> targetted for v3.4, but those you have queued currently are defintely
>>>> fixes.
>>>
>>> At this point in the release cycle, I would prefer to wait.
>>
>> It would be really great if this series could make it in for v3.3-rcX.
>> Without it, 3.3 will be unusable for any OMAP users that run the console
>> on the serial port. That's pretty much every OMAP user that runs mainline
>> kernels, AFAIK.
>
> Show me an OMAP user that actually runs a mainline kernel :)
>
We do for our codec and dsp development and the latest ones have given us fits lately :)

> What changeset(s) do you want me to take from my tty-next tree and put
> it in the tty-linus tree to be merged for the 3.3-final timeframe?
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>