From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: paul.eggleton@linux.intel.com, otavio@ossystems.com.br,
openembedded-core@lists.openembedded.org
Subject: [PATCH master, dylan, danny 0/1] kern-tools: make dash compliant
Date: Sun, 12 May 2013 21:06:13 -0700 [thread overview]
Message-ID: <cover.1368417050.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Here's an update of merge_config.sh for master, dylan and danny. The
changes to master and danny are identical, but we need two commits
versus one for dylan. As for danny, I ported only the changes that I
needed for dash compliance, and created a kern-tools branch to track
that change. So the patch for danny has a SRCREV update and a switch
to the danny kern-tools branch.
The patches break down like this:
master: zedd/kerntools-master
[PATCH 1/1] kern-tools: refresh and make dash compliant
dylan: zedd/kerntools-dylan
[PATCH dylan 1/2] kern-tools: anchor and delimit regexs
[PATCH dylan 2/2] kern-tools: refresh and make dash complian
danny: zedd/kerntools-danny
[PATCH danny] kern-tools: refresh and make dash compliant
The problem was this:
The separately packaged merge_config.sh in the kern-tools package was
missing upstream fixes, and in particular a change that ensures it is
dash compatible.
By grabbing that upstream commit and rebasing the existing patches on
top of the new baseline, we are up to date and working on systems
where /bin/sh is dash.
I've tested the kernel config on all branches, as well as busy box on
master and dylan. The before and after .configs are the same and we
are dash compliant. But it's worth doing some sanity tests, just in
case I messed up the juggling of the three branches!
cc: "Burton, Ross" <ross.burton@intel.com>
cc: Paul Eggleton <paul.eggleton@linux.intel.com>
cc: Otavio Salvador <otavio@ossystems.com.br>
[YOCTO #4473]
Cheers,
Bruce
The following changes since commit f7afeeb75993b159bb8959e0309bc5eb3978a8fb:
bitbake: bitbake-layers/tinfoil: Catch up with status -> recpiecache rename (2013-05-12 18:00:46 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kerntools-master
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kerntools-master
Bruce Ashfield (1):
kern-tools: refresh and make dash compliant
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.7.10.4
next reply other threads:[~2013-05-13 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 4:06 Bruce Ashfield [this message]
2013-05-13 4:06 ` [PATCH 1/1] kern-tools: refresh and make dash compliant Bruce Ashfield
2013-05-13 4:06 ` [PATCH dylan 1/2] kern-tools: anchor and delimit regexs Bruce Ashfield
2013-05-13 4:06 ` [PATCH dylan 2/2] kern-tools: refresh and make dash compliant Bruce Ashfield
2013-05-13 4:06 ` [PATCH danny] " 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.1368417050.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
--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