From: Cal Sullivan <california.l.sullivan@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/6] linux-yocto/4.1: update to v4.1.41
Date: Thu, 13 Jul 2017 13:57:19 -0700 [thread overview]
Message-ID: <73d8e805-380f-874b-82b2-7d8c6269d46f@intel.com> (raw)
In-Reply-To: <6c3f201c-aa8c-6384-d970-5057fb933b03@windriver.com>
It occurred with qemux86-64 rather than genericx86-64, so your new patch
for 4.1 should fix it.
---
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@windriver.com <mailto:bruce.ashfield@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
>
next prev parent reply other threads:[~2017-07-13 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 15:04 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2017-07-11 15:04 ` [PATCH 1/6] kernel-yocto: propagate configuration errors to bbclass Bruce Ashfield
2017-07-11 15:04 ` [PATCH 2/6] kernel-yocto/meta: smp configuration changes Bruce Ashfield
2017-07-11 15:04 ` [PATCH 3/6] linux-yocto/4.1: update to v4.1.41 Bruce Ashfield
2017-07-12 22:17 ` Burton, Ross
2017-07-12 22:39 ` Bruce Ashfield
2017-07-13 16:33 ` Bruce Ashfield
2017-07-13 16:40 ` Burton, Ross
2017-07-13 16:50 ` Bruce Ashfield
2017-07-13 20:57 ` Cal Sullivan [this message]
2017-07-14 1:57 ` Bruce Ashfield
2017-07-11 15:04 ` [PATCH 4/6] linux-yocto/4.4: update to v4.4.76 Bruce Ashfield
2017-07-11 15:04 ` [PATCH 5/6] linux-yocto/4.9: update to v4.9.36 Bruce Ashfield
2017-07-11 15:04 ` [PATCH 6/6] linux-yocto-dev: bump to 4.12+ Bruce Ashfield
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=73d8e805-380f-874b-82b2-7d8c6269d46f@intel.com \
--to=california.l.sullivan@intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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