Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: dvhart@linux.intel.com
Subject: Re: [PATCH 0/3] linux-yocto: 3.2.2 and 3.0.18 updates
Date: Thu, 02 Feb 2012 09:53:47 -0800	[thread overview]
Message-ID: <4F2ACDAB.5060103@intel.com> (raw)
In-Reply-To: <cover.1327952323.git.bruce.ashfield@windriver.com>

On 01/30/2012 12:02 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Two kernel updates in this pull request. The bigger change is the
> introduction/release of the 3.2 kernel repository. I've had this
> under test in one form or another for nearly two months now. It
> no only brings in a new kernel, but introduces some branching changes
> and audited kernel configuration fragments. This needs head to the
> servers now to allow add-on work to be completed.
>
> I've built and booted sato on all the emulated targets for the 3.2
> kernel.
>
> There is an associated set of kern-tools changes to support the
> branching in the 3.2 kernel repository, and the changes are fully
> compatible with the existing 3.0 tree.
>
> The second update is a refresh of the 3.0 tree to pickup 3.0.18, and
> to merge a set of pending features to that tree. The commit itself
> tells the story.
>
> I've built and booted this for all the emulated targets as well.
>
> The following changes since commit b719d7e10bdb5bb4fc9ef70256eb93f925fbda4b:
>
>    useradd: Ensure dependencies are only added for target recipes, not native or nativesdk (2012-01-27 16:59:56 +0000)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib zedd/kernel-oe
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe
>
> Bruce Ashfield (3):
>    kern-tools: import config audit and branch manipulation updates
>    linux-yocto: add kernel 3.2.2 support
>    linux-yocto: update to v3.0.18 + features
>
>   .../kern-tools/kern-tools-native_git.bb            |    2 +-
>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    8 ++--
>   meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb    |   37 ++++++++++++++++++
>   meta/recipes-kernel/linux/linux-yocto_3.0.bb       |   19 ++++-----
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb       |   41 ++++++++++++++++++++
>   5 files changed, 92 insertions(+), 15 deletions(-)
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.2.bb
>
Merged into OE-core

Thanks
	Sau!



      parent reply	other threads:[~2012-02-02 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 20:02 [PATCH 0/3] linux-yocto: 3.2.2 and 3.0.18 updates Bruce Ashfield
2012-01-30 20:02 ` [PATCH 1/3] kern-tools: import config audit and branch manipulation updates Bruce Ashfield
2012-01-30 20:02 ` [PATCH 2/3] linux-yocto: add kernel 3.2.2 support Bruce Ashfield
2012-01-30 20:02 ` [PATCH 3/3] linux-yocto: update to v3.0.18 + features Bruce Ashfield
2012-02-02 17:53 ` Saul Wold [this message]

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=4F2ACDAB.5060103@intel.com \
    --to=saul.wold@intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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