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: Thu, 27 Feb 2014 16:12:34 -0500 [thread overview]
Message-ID: <cover.1393535348.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
While I put the finishing touches on the 3.14 -dev kernel (and versioned
linux-yocto recipe), here are pending updates to the other supported
kernel versions, and a minor change to create consistency in branch
validation process.
I've kept all the incremental version (And LTSI) updates intact in this
series, since they represent build and validation points that I used
during the merges, and should be maintained in the history.
Sanity has passed across all the qemu* platforms, as well as builds for
the hardware references.
Cheers,
Bruce
The following changes since commit 5ab9d7e28f987fba8bab03bb7851c263f746c208:
security-flags: Avoid lttng-tools issue on arm (2014-02-26 13:48:21 +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 (4):
kernel-yocto: always checkout machine branch when existing
validate_branches
linux-yocto/3.10: update to v3.10.32
linux-yocto/3.4: update to v3.4.82 and latest LTSI
linux-yocto/3.10: integrate latest LTSI changes
meta/classes/kernel-yocto.bbclass | 37 ++++++++++------------
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++------
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 +++++-----
7 files changed, 47 insertions(+), 52 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-02-27 21:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 21:12 Bruce Ashfield [this message]
2014-02-27 21:12 ` [PATCH 1/4] kernel-yocto: always checkout machine branch when existing validate_branches Bruce Ashfield
2014-02-27 21:12 ` [PATCH 2/4] linux-yocto/3.10: update to v3.10.32 Bruce Ashfield
2014-02-27 21:12 ` [PATCH 3/4] linux-yocto/3.4: update to v3.4.82 and latest LTSI Bruce Ashfield
2014-02-27 21:12 ` [PATCH 4/4] linux-yocto/3.10: integrate latest LTSI changes Bruce Ashfield
-- 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
2015-09-29 14:31 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.1393535348.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 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.