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: Mon, 2 Mar 2015 16:36:37 -0500	[thread overview]
Message-ID: <cover.1425331960.git.bruce.ashfield@windriver.com> (raw)

Richard,

Here's my next round of incremental fixes and updates. All are relatively
minor, so there's no sense sitting on them while I work on some other
changes.

These two are tweaks to the Kconfig audit warnings that went into M3, and
will remove a config warning and the other will not uncessarily warn people
who've done nothing wrong :)

  linux-yocto: fix qemux86-64 config warning
  kernel-yocto: inhibit BSP description warnings for custom linux-yocto kernels

I also have some OcteonIII support additions to linux-yocto-3.14, and finally
a minor patch performance improvement. We aren't done on this front, but again,
no sense sitting on changes.

Cheers,

Bruce


The following changes since commit bf1a68e97f2069a4f66664c351d4bafd416358eb:

  taglib: Fix cmake floating dependency on boost (2015-03-02 18:06:53 +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: fix qemux86-64 config warning
  kernel-yocto: inhibit BSP description warnings for custom linux-yocto kernels
  linux-yocto/3.14: OcteonIII support
  kern-tools: improve patch application performance

 meta/classes/kernel-yocto.bbclass                       | 13 +++++++------
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb        |  5 +++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb      |  3 ++-
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb      |  3 ++-
 meta/recipes-kernel/linux/linux-yocto.inc               |  1 +
 meta/recipes-kernel/linux/linux-yocto_3.14.bb           | 17 +++++++++--------
 meta/recipes-kernel/linux/linux-yocto_3.19.bb           |  3 ++-
 8 files changed, 27 insertions(+), 20 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-03-02 21:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 21:36 Bruce Ashfield [this message]
2015-03-02 21:36 ` [PATCH 1/4] linux-yocto: fix qemux86-64 config warning Bruce Ashfield
2015-03-02 21:36 ` [PATCH 2/4] kernel-yocto: inhibit BSP description warnings for custom linux-yocto kernels Bruce Ashfield
2015-03-02 21:36 ` [PATCH 3/4] linux-yocto/3.14: OcteonIII support Bruce Ashfield
2015-03-02 21:36 ` [PATCH 4/4] kern-tools: improve patch application performance Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2025-04-10 18:55 [PATCH 0/4] kernel-yocto: consolidated pull request 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
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
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.1425331960.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