[yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

Bruce Ashfield bruce.ashfield at windriver.com
Tue Nov 6 18:07:56 PST 2018


On 2018-11-06 8:07 p.m., akuster808 wrote:
> 
> On 11/6/18 2:42 PM, Bruce Ashfield wrote:
>> On 2018-11-06 5:10 PM, akuster808 wrote:
>>>
>>> On 11/6/18 2:05 PM, Khem Raj wrote:
>>>> On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster<akuster808 at gmail.com>
>>>> wrote:
>>>>> Signed-off-by: Armin Kuster<akuster at mvista.com>
>>>>> ---
>>>>>    kver | 2 +-
>>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/kver b/kver
>>>>> index 7b008cd..5ccc572 100644
>>>>> --- a/kver
>>>>> +++ b/kver
>>>>> @@ -1 +1 @@
>>>>> -v4.4.141
>>>>> +v4.4.147
>>>> why not 4.4.162
>>>
>>> because linux-yocto-4.4
>>> <http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/> is not
>>> at 4.4.162. I am just trying to use the latest in that kernel repo.
>>
>> Did you want .162 ? I have a whole set of -stable updates staged
>> here, but haven't pushed anything since releases are imminent.
> 
> We are a day or two away from freezing for a Rocko QA run so if I can
> get it sometime tomorrow, I should be able to  get some runtime on that
> update otherwise no need to rush things.

If you check the 4.4 tree, and the kernel-cache, I've pushed the
latest set of -stable updates.

Up to you if you want to bump the SRCREVs to pick them up, but I've
validated them with my builds/boots.

Bruce

> 
> - armin
> 
>>
>> But in the case of 4.4, I could lift my freeze, given that the kernel
>> recipe isn't active in master, hence the release schedule is
>> different.
>>
> 
>> Bruce
>>
>>>
>>>
>>> - armin
>>>
>>>>> -- 
>>>>> 2.7.4
>>>>>
>>>>> -- 
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto at yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>
> 



More information about the yocto mailing list