All of lore.kernel.org
 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/5] linux-yocto: consolidated pull request
Date: Tue, 24 Mar 2015 14:57:48 -0400	[thread overview]
Message-ID: <cover.1427222980.git.bruce.ashfield@windriver.com> (raw)

Hi all,

Here is the latest linux-yocto consolidated pull request. It is a mix of
kernel version -stable imports (CVEs and fixes), kernel configuration 
changes, a documentation update and kernel configuration enhancement.

The -stable updates are routine, and I build/boot tested them here
(with my fixup commits being evidence). These are ready for a round of
autobuilder/soak testing.

The only other change is the addition of the ability to use a defconfig
that is maintained within a kernel tree. This enhacement request came
from the raspberrypi2 maintainers. We went through a few revisions and
test cycles on this (see YOCTO: 7474 for the details). 

The final result has no impact on existing configuration workflows, but
does allow an in-tree config to be copied out into WORKDIR and then
incorporated with other fragments as part of kconfig processing. A new
variable is introduced for specifying the defconfig KBUILD_DEFCONFIG,
and I'll work with Scott to make sure this is documented in the 
appropriate locations.

Cheers,

Bruce


The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:

  yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +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 (5):
  kernel-yocto: allow in-tree defconfigs
  linux-yocto/3.19: configuration updates and stable import
  linux-yocto/3.14: integrate korg stable and meta data changes
  linux-yocto/3.19: fixes for Intel core warnings
  skeleton: clarify linux-yocto-custom workflow

 .../recipes-kernel/linux/linux-yocto-custom.bb     |  6 ++--
 meta/classes/kernel-yocto.bbclass                  | 39 ++++++++++++++++++++--
 meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb   |  8 ++---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 20 +++++------
 meta/recipes-kernel/linux/linux-yocto_3.19.bb      | 20 +++++------
 7 files changed, 69 insertions(+), 36 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-03-24 18:57 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 18:57 Bruce Ashfield [this message]
2015-03-24 18:57 ` [PATCH 1/5] kernel-yocto: allow in-tree defconfigs Bruce Ashfield
2015-03-24 18:57 ` [PATCH 2/5] linux-yocto/3.19: configuration updates and stable import Bruce Ashfield
2015-03-24 18:57 ` [PATCH 3/5] linux-yocto/3.14: integrate korg stable and meta data changes Bruce Ashfield
2015-03-24 18:57 ` [PATCH 4/5] linux-yocto/3.19: fixes for Intel core warnings Bruce Ashfield
2015-04-13 23:11   ` Martin Jansa
2015-03-24 18:57 ` [PATCH 5/5] skeleton: clarify linux-yocto-custom workflow Bruce Ashfield
2015-03-25  9:26 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2015-03-25 12:13   ` Bruce Ashfield
2015-03-25 13:26     ` Bruce Ashfield
2015-03-25 13:52       ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29  1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04  8:30 ` Richard Purdie
2020-05-04 12:56   ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01  1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30   ` Bruce Ashfield
2015-05-02  8:13     ` Martin Jansa
2015-05-03  2:50       ` Bruce Ashfield
2015-05-06 14:42         ` Martin Jansa
2015-05-06 14:58           ` Bruce Ashfield
2015-05-06 15:33             ` Martin Jansa
2015-05-06 15:44               ` Richard Purdie
2015-05-06 16:07                 ` Martin Jansa
2015-05-06 17:46                   ` Bruce Ashfield
2015-05-06 21:32                     ` Richard Purdie
2015-05-06 22:49                       ` Martin Jansa
2015-05-07 15:33                         ` Bruce Ashfield
2015-05-07  6:33               ` Khem Raj
2015-05-02  9:00     ` Richard Purdie
2015-05-03  2:53       ` Bruce Ashfield
2015-05-03  3:52       ` Bruce Ashfield
2015-05-03 10:48         ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04  4:36   ` Bruce Ashfield
2015-05-04 15:01   ` Bruce Ashfield
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24  6:33 ` Saul Wold
2013-08-24 13:34   ` Bruce Ashfield
2013-08-24 13:45     ` Bruce Ashfield
2013-08-24 13:50       ` Saul Wold
2013-08-24 13:53         ` Bruce Ashfield
2013-08-24 14:47         ` Bruce Ashfield
2013-08-24 14:59         ` Bruce Ashfield
2013-08-24 16:05         ` Bruce Ashfield
2012-02-05  6:31 Bruce Ashfield
2012-02-08  4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13  6:01 ` Saul Wold

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.1427222980.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.