[OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

Bruce Ashfield bruce.ashfield at gmail.com
Fri Jul 14 01:57:05 UTC 2017


On Thu, Jul 13, 2017 at 4:57 PM, Cal Sullivan <
california.l.sullivan at intel.com> wrote:

> It occurred with qemux86-64 rather than genericx86-64, so your new patch
> for 4.1 should fix it.
>

that explains my confusion. I wonder if I wandered into the wrong
autobuilder link .. I did have
to browse around a bit :D

Bruce


>
> ---
> Cal
>
>
> On 07/13/2017 09:50 AM, Bruce Ashfield wrote:
>
>> On 07/13/2017 12:40 PM, Burton, Ross wrote:
>>
>>>
>>> On 13 July 2017 at 17:33, Bruce Ashfield <bruce.ashfield at windriver.com
>>> <mailto:bruce.ashfield at windriver.com>> wrote:
>>>
>>>     How would you like the fix, a completely new patch, or an incremental
>>>     fix on my branch ?
>>>
>>>
>>>
>> Sent.
>>
>> Note: It says "v2", but I did change the shortlog to reference 4.1.42
>> versus 4.1.41.
>>
>> Since I'm still not building AUTOREV for this (I'll start that now to
>> try and trigger the issue), the fix is by visual inspection only.
>>
>> Anyone building poky-lsb by the SRCREVs should still get 4.1.39 versus
>> this updated kernel. SRCREV updates to the yocto-bsp layer still need
>> to follow.
>>
>> Bruce
>>
>> A replacement patch please, it's not in master yet.
>>>
>>> Ross
>>>
>>
>>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170713/b646e953/attachment-0002.html>


More information about the Openembedded-core mailing list