From: akuster808 <akuster808@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147
Date: Tue, 6 Nov 2018 17:07:01 -0800 [thread overview]
Message-ID: <1c979ece-ba16-454a-bebb-5a81fcb455c0@gmail.com> (raw)
In-Reply-To: <1a3be576-c416-2c6a-6b0d-674b61a1363c@windriver.com>
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@gmail.com>
>>> wrote:
>>>> Signed-off-by: Armin Kuster<akuster@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.
- 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@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2018-11-07 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:56 [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147 Armin Kuster
2018-11-06 22:05 ` Khem Raj
2018-11-06 22:10 ` akuster808
2018-11-06 22:42 ` Bruce Ashfield
2018-11-07 1:07 ` akuster808 [this message]
2018-11-07 2:07 ` Bruce Ashfield
2018-11-07 1:08 ` Khem Raj
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=1c979ece-ba16-454a-bebb-5a81fcb455c0@gmail.com \
--to=akuster808@gmail.com \
--cc=bruce.ashfield@windriver.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.