Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Fri,  2 Dec 2016 16:09:21 -0500	[thread overview]
Message-ID: <cover.1480711764.git.bruce.ashfield@windriver.com> (raw)

Hi all,

This pull request is mainly to fix a couple of bugs that were reported
on the mailing list recently, but it also includes some kernel version
updates that I *think* I sent previously.

  kern-tools: fix processing for no branch meta-data
  kernel-yocto: exit on non-zero return code

Those two changes complete the error handling in the tools to display
a (more) helpful message to the user, and also to fix an important
use case where meta-data is applied to a kernel without new branches
being created.

I test built this against the rpi, and all is well.

Cheers,

Bruce


The following changes since commit 9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a:

  bitbake: ast: remove BBVERSIONS support (2016-11-30 15:48:10 +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 (4):
  linux-yocto/4.8: update to v4.8.10
  linux-yocto-dev: update to 4.9-rcX
  kern-tools: fix processing for no branch meta-data
  kernel-yocto: exit on non-zero return code

 meta/classes/kernel-yocto.bbclass                    |  1 -
 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-dev.bb         |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb      |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.8.bb         | 20 ++++++++++----------
 6 files changed, 18 insertions(+), 19 deletions(-)

-- 
2.5.0



             reply	other threads:[~2016-12-02 21:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 21:09 Bruce Ashfield [this message]
2016-12-02 21:09 ` [PATCH 1/4] linux-yocto/4.8: update to v4.8.10 Bruce Ashfield
2016-12-02 21:09 ` [PATCH 2/4] linux-yocto-dev: update to 4.9-rcX Bruce Ashfield
2016-12-02 21:09 ` [PATCH 3/4] kern-tools: fix processing for no branch meta-data Bruce Ashfield
2016-12-06 21:14   ` Patrick Ohly
2016-12-06 23:02     ` Paul Barker
2016-12-07 15:11       ` Trevor Woerner
2016-12-07 15:14         ` Bruce Ashfield
2016-12-07 16:18         ` Bruce Ashfield
2016-12-07 18:05           ` Trevor Woerner
2016-12-07 23:50             ` Trevor Woerner
2016-12-08  3:23               ` Bruce Ashfield
2016-12-08 15:27               ` Bruce Ashfield
2016-12-02 21:09 ` [PATCH 4/4] kernel-yocto: exit on non-zero return code Bruce Ashfield
2016-12-06 19:32 ` [PATCH 0/4] kernel-yocto: consolidated pull request Trevor Woerner
  -- strict thread matches above, loose matches on Subject: below --
2025-04-10 18:55 bruce.ashfield
2025-04-10 20:24 ` Richard Purdie
2020-08-03 12:30 Bruce Ashfield
2020-03-04 14:55 bruce.ashfield
2019-12-30  3:07 bruce.ashfield
2015-03-02 21:36 Bruce Ashfield
2013-05-31  3:28 Bruce Ashfield
2013-05-31  6:14 ` Saul Wold
2013-05-31  7:07   ` Richard Purdie
2013-05-31 12:29     ` 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.1480711764.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