All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Sullivan, California L" <california.l.sullivan@intel.com>,
	"richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"WOLD, SAUL" <saul.wold@intel.com>
Subject: Re: [v2 PATCH 0/8] linux-yocto: consolidated pull request
Date: Mon, 29 Feb 2016 18:38:21 -0500	[thread overview]
Message-ID: <56D4D66D.3030303@windriver.com> (raw)
In-Reply-To: <48F3FC2919BF894DA92986D5D64EA12801A6424A@ORSMSX103.amr.corp.intel.com>

On 2016-02-29 6:01 PM, Sullivan, California L wrote:
> On 02/29/2016 02:10 PM, Bruce Ashfield wrote:
>> Hi all,
>>
>> v2: actually cc oe-core on the series.
>>
>> Here is the consolidated pull request for linux-yocto 4.1 and 4.4. Most of the
>> changes are updates to -stable for the kernels, and the others are updates for
>> specific boards.
>>
>> I've been building and booting these for qemu*, but of course, more mileage and
>> combinations in the autobuilder is best.
>>
>> Some things to note:
>>
>>   - We have some refactored kernel configuration updates to the base/core policy
>>     of the standard kernel, with a new "developer" kernel type being available,
>>     leaving standard as a smaller variant. Existing board configs have been
>>     flipped to use developer, so they'll see no change, leaving new board configs
>>     to take advantage of the smaller, standard kernel type.
> It looks like this change hasn't been integrated into the kernel cache yet.

It has. I just forgot to add the patch to the series :) I meant to send
a follow up, but got distracted!

Bruce

>
> ---
> Cal Sullivan
>
>>
>>   - The yocto reference BSPs haven't been updated yet, and we need to find
>>     someone with the h/w to do the updates. These may just have to stay on
>>     4.1 LTSI for this cycle.
>>
>>   - We are still seeing the 32 bit x86 X issue on the 4.4 kernel , with a splat on
>>     boot up. I've tried to bisect this twice, leading to inconclusive results, but
>>     regardless, I need to march 4.4 onto the latest -stable, and we'll continue
>>     looking into this issue in the M4 timeframe.
>>
>>   - There still seem to be some races in perf, and something is up with sstate
>>     and the kexec/kboot builds using meta-initramfs and linux-yocto-tiny-kexecboot.
>>     Now that these updates are out, I'll revisit them and hold any stable updates
>>     (unless there are significant CVEs) in the M4 cycle.
>>
>> Cheers,
>>
>> Bruce
>>
>> The following changes since commit 4006a7f2762ccd5dcbc6cdff49482d4387a73261:
>>
>>    sanity: Fix int verses string reference (2016-02-28 22:54:09 +0000)
>>
>> are available in the git repository at:
>>
>>    git://git.pokylinux.org/poky-contrib zedd/kernel
>>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>
>> Bruce Ashfield (8):
>>    linux-yocto/4.1: Galileo updates
>>    linux-yocto/4.1: clkdev updates
>>    linux-yocto/4.1: update to 4.1.18
>>    linux-yocto/4.4: yaffs2 build fixes
>>    linux-yocto: braswell: Remove feature and move DRM_I915_PRELIMINARY_HW_SUPPORT option
>>    linux-yocto/4.4: update to -stable 4.4.2
>>    linux-yocto/4.1: iwlwifi: mvm: don't allow sched scans without matches to be started
>>    linux-yocto/4.4: update to 4.4.3
>>
>>   meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
>>   meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  6 +++---
>>   meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
>>   meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  6 +++---
>>   meta/recipes-kernel/linux/linux-yocto_4.1.bb      | 20 ++++++++++----------
>>   meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 20 ++++++++++----------
>>   6 files changed, 32 insertions(+), 32 deletions(-)
>>
>



  reply	other threads:[~2016-02-29 23:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 22:10 [v2 PATCH 0/8] linux-yocto: consolidated pull request Bruce Ashfield
2016-02-29 22:10 ` [PATCH 1/8] linux-yocto/4.1: Galileo updates Bruce Ashfield
2016-02-29 22:10 ` [PATCH 2/8] linux-yocto/4.1: clkdev updates Bruce Ashfield
2016-02-29 22:10 ` [PATCH 3/8] linux-yocto/4.1: update to 4.1.18 Bruce Ashfield
2016-02-29 22:10 ` [PATCH 4/8] linux-yocto/4.4: yaffs2 build fixes Bruce Ashfield
2016-02-29 22:10 ` [PATCH 5/8] linux-yocto: braswell: Remove feature and move DRM_I915_PRELIMINARY_HW_SUPPORT option Bruce Ashfield
2016-02-29 22:10 ` [PATCH 6/8] linux-yocto/4.4: update to -stable 4.4.2 Bruce Ashfield
2016-02-29 22:10 ` [PATCH 7/8] linux-yocto/4.1: iwlwifi: mvm: don't allow sched scans without matches to be started Bruce Ashfield
2016-02-29 22:10 ` [PATCH 8/8] linux-yocto/4.4: update to 4.4.3 Bruce Ashfield
2016-02-29 23:01 ` [v2 PATCH 0/8] linux-yocto: consolidated pull request Sullivan, California L
2016-02-29 23:38   ` Bruce Ashfield [this message]
2016-02-29 23:42   ` 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=56D4D66D.3030303@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=california.l.sullivan@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@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 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.