From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/4] linux-yocto: consolidated update
Date: Wed, 15 Aug 2012 16:06:19 -0400 [thread overview]
Message-ID: <cover.1345059176.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's a consolidated update that I've had under test in one
way or another for 3 weeks now. Tom Z and others have also been
using parts of this for their work, so it has seen a reasonably
wide set of testers.
This series further streamlines working with linux-yocto* based
recipes/repositories by breaking the last branch based triggers
in the tooling. Branches were the most important piece of
information when working with the tools and a linux-yocto repository,
but this has now been generalized, and BSP descriptions (among
other things) are now found by MACHINE and kernel type only.
With this, KBRANCH now becomes what it was supposed to be, an
human readible indication of the branch that is supposed to be
built, and one that the kern-tools will validate. If that branch
is not validated, an error is thrown. If the default branch is
left as-is, then the in-tree description leaves you on the
proper branch and all is well.
I also have a collection of bug fixes to the tools, including
support for having a meta branch not called 'meta'.
I'd recommend that this go through some AB tests, and I'll be
around if there's a corner case that I managed to miss.
Cheers,
Bruce
The following changes since commit ee11e7ac55fa41cb69e9519f3e879a1746c4cf33:
linux-yocto/meta-yocto/3.4: BSP, uprobes, config and cleanups (2012-08-15 13:52:00 -0400)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-dev
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-dev
Bruce Ashfield (4):
linux-yocto: make KBRANCH the exception and not the rule
linux-yocto/3.4: remove explicit KBRANCH designations
linux-yocto: explicitly export KMETA to scripts
kern-tools: fixes (branching,buildall) + cleanups (checkpoint,cleaner)
meta/classes/kernel-yocto.bbclass | 93 ++++++++++++++------
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 11 +--
3 files changed, 69 insertions(+), 37 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-08-15 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 20:06 Bruce Ashfield [this message]
2012-08-15 20:06 ` [PATCH 1/4] linux-yocto: make KBRANCH the exception and not the rule Bruce Ashfield
2012-08-18 12:07 ` Richard Purdie
2012-08-18 14:33 ` Bruce Ashfield
2012-08-18 15:29 ` Richard Purdie
2012-08-15 20:06 ` [PATCH 2/4] linux-yocto/3.4: remove explicit KBRANCH designations Bruce Ashfield
2012-08-15 20:06 ` [PATCH 3/4] linux-yocto: explicitly export KMETA to scripts Bruce Ashfield
2012-08-15 20:06 ` [PATCH 4/4] kern-tools: fixes (branching, buildall) + cleanups (checkpoint, cleaner) Bruce Ashfield
2012-08-18 16:57 ` [PATCH 0/4] linux-yocto: consolidated update Richard Purdie
2012-08-18 17:15 ` Bruce Ashfield
2012-08-18 22:18 ` Richard Purdie
2012-08-19 4:44 ` Bruce Ashfield
2012-08-19 9:47 ` Richard Purdie
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.1345059176.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 \
/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