From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] kernel-yocto: yet another set of changes
Date: Fri, 9 Dec 2016 14:27:58 -0500 [thread overview]
Message-ID: <cover.1481311536.git.bruce.ashfield@windriver.com> (raw)
In the never ending stream of kernel pull requests, we have an update
to the latest 4.8-rt from Paul Gortmaker.
And as it turns out, my effor in making sure that meta data errors were
trapped was a bit to simple. I do in fact need the set +e to allow some
of the other checks in the routine to follow else clauses.
So there's a patch in this pull that puts the +e back, and I explicitly
trap and error if a meta data command fails.
Cheers,
Bruce
The following changes since commit 36e178a62f04e7f2611b26964efe46b9af97189a:
linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.8 (2016-12-09 08:54:07 +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 (2):
linux-yocto/4.8: update to -rt7
kernel-yocto: explicitly trap subcommand errors
meta/classes/kernel-yocto.bbclass | 7 +++++++
meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.8.bb | 2 +-
4 files changed, 11 insertions(+), 4 deletions(-)
--
2.5.0
next reply other threads:[~2016-12-09 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 19:27 Bruce Ashfield [this message]
2016-12-09 19:27 ` [PATCH 1/2] linux-yocto/4.8: update to -rt7 Bruce Ashfield
2016-12-09 19:28 ` [PATCH 2/2] kernel-yocto: explicitly trap subcommand errors 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.1481311536.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.