From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] kernel-yocto: consolidated pull request
Date: Tue, 5 Feb 2013 10:56:32 -0500 [thread overview]
Message-ID: <cover.1360079063.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's the latest batch of kernel changes. In this series, we are moving the
linux-yocto-dev recipe out of poky-extras into a more visible location (using
the scheme agreed upon to avoid AUTOREV network access). I also have a
cleanup patch to existing KERNEL_FEATURES references, and finally a bump of
the 3.4 and 3.4-rt versions.
Details follow:
[PATCH 1/3] linux-yocto/dev: linux-yocto development tree tracking recipe
The linux-yocto-dev recipe uses the upstream tracking linux-yocto-dev repository.
Since this tree is frequently updated, and periodically rebuilt, AUTOREV is used
to track its contents.
This recipe is just like other linux-yocto variants, with the only difference
being that to avoid network access during initial parsing, static SRCREVs are
provided and overridden if the preferred kernel provider is linux-yocto-dev.
[PATCH 2/3] linux-yocto/3.4: update to v3.4.28, 3.4.28-rt40
Updating the linux-yocto_3.4 SRCREVs to pick up the 3.4.28 -stable update
as well as the 3.4.28-rt40 refresh.
[PATCH 3/3] linux-yocto: KERNEL_FEATURES should reference full scc files
Some existing KERNEL_FEATURE references use a shorcut notation, but mapping
these shortcuts to actual .scc files in the tree are not obvious. So we clarify
where they are found by referencing the full .scc filename in the KERNEL_FEATURE
addtions.
Cheers,
Bruce
The following changes since commit 7e9cb437b1b720e656f4a33f73c07c5dc7356a2c:
dropbear: fix RPROVIDES (2013-02-04 23:31:02 +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 (3):
linux-yocto/dev: linux-yocto development tree tracking recipe
linux-yocto/3.4: update to v3.4.28, 3.4.28-rt40
linux-yocto: KERNEL_FEATURES should reference full scc files
meta/recipes-kernel/linux/linux-yocto-dev.bb | 48 +++++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 8 ++--
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 18 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 8 ++--
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 28 ++++++------
6 files changed, 81 insertions(+), 35 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-yocto-dev.bb
--
1.7.10.4
next reply other threads:[~2013-02-05 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 15:56 Bruce Ashfield [this message]
2013-02-05 15:56 ` [PATCH 1/3] linux-yocto/dev: linux-yocto development tree tracking recipe Bruce Ashfield
2013-02-05 15:56 ` [PATCH 2/3] linux-yocto/3.4: update to v3.4.28, 3.4.28-rt40 Bruce Ashfield
2013-02-05 15:56 ` [PATCH 3/3] linux-yocto: KERNEL_FEATURES should reference full scc files Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 16:14 [PATCH 0/3] kernel-yocto: consolidated pull request bruce.ashfield
2020-08-21 19:02 Bruce Ashfield
2022-10-19 3:39 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.1360079063.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