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: Wed, 26 Jun 2013 09:40:25 -0400 [thread overview]
Message-ID: <cover.1372253710.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's a collection of four patches that I've queued in the
past few days. My normal smoke testing passed here.
These are a collection of version refreshes, and configuration
changes. Nothing major. Once these are merged, the stage is
set for more 1.5 development items.
Everything is pretty self explanitory, or was discussed on
the mailing list, so I'll keep it to a summary here. Let me
know if there are any concerns.
[PATCH 1/4] linux-yocto/3.4: allow kernel feature _appends to be overriden
[PATCH 2/4] linux-yocto/3.8: add USB screen configuration and net sched options
[PATCH 3/4] linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed
[PATCH 4/4] linux-yocto-dev: bump version to 3.10+
Cheers,
Bruce
The following changes since commit 8e9501ffa8726d69412d669580d787ffedb88d34:
populate_sdk_base, adt_installer: abort install if path contains spaces (2013-06-25 17:59:17 +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/3.4: allow kernel feature _appends to be overriden
linux-yocto/3.8: add USB screen configuration and net sched options
linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed
linux-yocto-dev: bump version to 3.10+
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 17 +++++++++--------
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 2 +-
7 files changed, 16 insertions(+), 15 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-06-26 13:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 13:40 Bruce Ashfield [this message]
2013-06-26 13:40 ` [PATCH 1/4] linux-yocto/3.4: allow kernel feature _appends to be overriden Bruce Ashfield
2013-06-26 13:40 ` [PATCH 2/4] linux-yocto/3.8: add USB screen configuration and net sched options Bruce Ashfield
2013-06-26 13:40 ` [PATCH 3/4] linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247ed Bruce Ashfield
2013-06-26 13:40 ` [PATCH 4/4] linux-yocto-dev: bump version to 3.10+ 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
2014-02-27 21:12 Bruce Ashfield
2013-11-04 5:56 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.1372253710.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