From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: tom.zanussi@intel.com, openembedded-core@lists.openembedded.org,
saul.wold@intel.com
Subject: [PATCH 0/3 v2] linux-yocto: linux-yocto: intel staging and bxt backports
Date: Fri, 27 May 2016 10:32:19 -0400 [thread overview]
Message-ID: <cover.1464359230.git.bruce.ashfield@windriver.com> (raw)
Hi all,
This pull request superceeds my other request by the same subject.
The only difference is that I now have a 3rd patch from Tom, that reverts
the branch name change for generic/qemux86*, since we didn't intend for
them to use the intel staging branches.
Cheers,
Bruce
The following changes since commit 2718e843b3502afa1e21510bb6b9c4720f75124c:
yocto-bsps: update to 4.4.11 (2016-05-26 11:34:14 +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 (3):
linux-yocto:4.4: broxton backports
linux-yocto: create intel branches
linux-yocto: only use intel branches for optimized platforms
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 18 +++++++++---------
6 files changed, 17 insertions(+), 17 deletions(-)
--
2.5.0
next reply other threads:[~2016-05-27 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:32 Bruce Ashfield [this message]
2016-05-27 14:32 ` [PATCH 1/3] linux-yocto:4.4: broxton backports Bruce Ashfield
2016-05-27 14:32 ` [PATCH 2/3] linux-yocto: create intel branches Bruce Ashfield
2016-05-27 14:32 ` [PATCH 3/3] linux-yocto: only use intel branches for optimized platforms 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=cover.1464359230.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
--cc=tom.zanussi@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