Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] linux-yocto: consolidated pull request
Date: Tue, 29 Sep 2015 10:31:31 -0400	[thread overview]
Message-ID: <cover.1443536748.git.bruce.ashfield@windriver.com> (raw)

Hi all,

Here is the latest round of linux-yocto related changes.

The first three are integrations of BSP patches/fixes, and a -stable
update for 4.1. I've built and booted them here. 

The only trick with the axxia BSP integration is that there's a branch
rename for standard/preempt-rt to standard/preempt-rt base, so when I 
push the rename, builds of -rt won't be happy until the related recipe
change merges to the tree. But otherwise, it is pretty standard stuff.

Khem noticed that in my quest to speed up and simplify the way that
layers patch and configure the tree, that I went too far and broke 
multiple layers patching the tree.

So the final fix is a tweak to the tools to address that, which both
Khem and I have tested.

Cheers,

bruce


The following changes since commit f78f90240a3041be426c6ba9085849352164ee8b:

  bitbake: prserv/serv.py: Better messaging when starting/stopping the server with port=0 (2015-09-28 12:00:33 +0100)

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 (4):
  linux-yocto-rt/4.1: integrate axxia BSP
  linux-yocto/4.1: update to 4.1.8 -stable
  linux-yocto/4.1: braswell bug fixes
  kern-tools: fix multi-layer patch application

 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb      |  8 ++++----
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.1.bb         | 20 ++++++++++----------
 4 files changed, 18 insertions(+), 18 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-09-29 14:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 14:31 Bruce Ashfield [this message]
2015-09-29 14:31 ` [PATCH 1/4] linux-yocto-rt/4.1: integrate axxia BSP Bruce Ashfield
2015-09-29 14:31 ` [PATCH 2/4] linux-yocto/4.1: update to 4.1.8 -stable Bruce Ashfield
2015-09-29 14:31 ` [PATCH 3/4] linux-yocto/4.1: braswell bug fixes Bruce Ashfield
2015-09-29 14:31 ` [PATCH 4/4] kern-tools: fix multi-layer patch application Bruce Ashfield
2015-09-29 17:07   ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2022-02-13  1:23 [PATCH 0/4] linux-yocto: consolidated pull request bruce.ashfield
2021-06-27 14:13 Bruce Ashfield
2021-01-12 22:14 Bruce Ashfield
2019-03-01  5:34 bruce.ashfield
2014-02-27 21:12 Bruce Ashfield
2013-11-04  5:56 Bruce Ashfield
2013-06-26 13:40 Bruce Ashfield
2012-11-21 21:32 Bruce Ashfield
2012-12-05 15:48 ` Burton, Ross
2012-12-05 16:06   ` Tom Zanussi
2012-12-05 16:27     ` Richard Purdie
2012-12-05 16:51       ` Darren Hart
2012-12-05 16:57       ` Tom Zanussi
2012-07-03 15:14 Bruce Ashfield
2012-07-05 17:44 ` Saul Wold
2011-12-22 18:05 Bruce Ashfield
2012-01-03 21:14 ` Saul Wold

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=cover.1443536748.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox