Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org,
	saul.wold@intel.com
Subject: [PATCH 0/2] linux-yocto/3.2: minor -rt increment and fixes
Date: Tue, 6 Mar 2012 10:24:31 -0500	[thread overview]
Message-ID: <cover.1331047183.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

This is another kernel SRCREV update that should be stacked on the
end of my other pending patches. I've kept everything separate so
we can track the incremental changes.

This one is a minor update to the 3.2 tree.

  - there were a few config files that moved between 3.0 and 3.2
    and I'm adjusting the BSPs to match
  - 3.2.9-rt16 came out with a fix we want, so I've bumped the
    3.2 rt BSPs to pick it up.

cc: Darren Hart <dvhart@linux.intel.com>

Cheers,

Bruce

The following changes since commit 3e07ca64df8b16348520fa72d88f0ef54b5fee77:

  linux-yocto/meta-yocto: v3.2.9, v3.0.23 + fixes and updates (2012-03-06 10:18:11 -0500)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel-3.2
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-3.2

Bruce Ashfield (2):
  linux-yocto/meta: fix incorrect config references
  linux-yocto/rt: udpate SRCREVs to 3.2.9-rt16

 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |    6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.2.bb    |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
1.7.4.1




             reply	other threads:[~2012-03-06 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 15:24 Bruce Ashfield [this message]
2012-03-06 15:24 ` [PATCH 1/2] linux-yocto/meta: fix incorrect config references Bruce Ashfield
2012-03-06 15:24 ` [PATCH 2/2] linux-yocto/rt: udpate SRCREVs to 3.2.9-rt16 Bruce Ashfield
2012-03-13 15:59 ` [PATCH 0/2] linux-yocto/3.2: minor -rt increment and fixes 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.1331047183.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.com \
    /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