Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] denzil pull request 4
Date: Wed, 20 Jun 2012 16:05:47 -0700	[thread overview]
Message-ID: <cover.1340233133.git.scott.a.garman@intel.com> (raw)

Hello,

This is the fourth pull request for the oe-core denzil branch, based on
a set of commits I've been testing from my sgarman/denzil-next branch.
At the time I'm composing this, my previous pull request hasn't been
merged yet, so I created this pull against my previous branch,
sgarman/denzil-next-pull3.

Once this branch gets merged, we will generate the first denzil release
candidate, which will undergo a full QA pass.

These commits have undergone the following testing on the autobuilder:

nightly:
http://autobuilder.yoctoproject.org:8010/builders/nightly/builds/521

nightly-multilib:
http://autobuilder.yoctoproject.org:8010/builders/nightly-multilib/builds/117

nightly-non-gpl3:
http://autobuilder.yoctoproject.org:8010/builders/nightly-non-gpl3/builds/118

nightly-tiny:
http://autobuilder.yoctoproject.org:8010/builders/nightly-tiny/builds/100

nightly-meta-intel (still finishing):
http://autobuilder.yoctoproject.org:8010/builders/nightly-meta-intel/builds/107

I'll note these tests were done with the poky-based tree.

Scott

The following changes since commit eedf8f8d9a7324b33dec71a5c52f8d980dc78752:

  eglibc: added ac_cv_path_ to CACHED_CONFIGUREVARS (2012-06-15 09:40:13 -0700)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib sgarman/denzil-next-testing
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgarman/denzil-next-pull4

Anders Darander (1):
  qt4-embedded: fix QT_ARCH usage in QT_CONFIG_FLAGS

Bruce Ashfield (5):
  linux-yocto/3.2: configuration and pch merge
  linux-yocto: intel BSP config changes
  linux-yocto: policy cleanups
  linux-yocto/3.2: update to v3.2.18
  linux-yocto/3.0: update to v3.0.32

 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb   |    6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb   |    8 ++++----
 meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |    6 +++---
 meta/recipes-kernel/linux/linux-yocto_3.0.bb      |   16 ++++++++--------
 meta/recipes-kernel/linux/linux-yocto_3.2.bb      |   18 +++++++++---------
 meta/recipes-qt/qt4/qt4-embedded.inc              |    2 +-
 6 files changed, 28 insertions(+), 28 deletions(-)

-- 
1.7.9.5




             reply	other threads:[~2012-06-20 23:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 23:05 Scott Garman [this message]
2012-06-20 23:05 ` [PATCH 1/6] linux-yocto/3.2: configuration and pch merge Scott Garman
2012-06-20 23:05 ` [PATCH 2/6] linux-yocto: intel BSP config changes Scott Garman
2012-06-20 23:05 ` [PATCH 3/6] linux-yocto: policy cleanups Scott Garman
2012-06-20 23:05 ` [PATCH 4/6] linux-yocto/3.2: update to v3.2.18 Scott Garman
2012-06-20 23:05 ` [PATCH 5/6] linux-yocto/3.0: update to v3.0.32 Scott Garman
2012-06-20 23:05 ` [PATCH 6/6] qt4-embedded: fix QT_ARCH usage in QT_CONFIG_FLAGS Scott Garman
2012-06-21 11:00 ` [PATCH 0/6] denzil pull request 4 Richard Purdie

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.1340233133.git.scott.a.garman@intel.com \
    --to=scott.a.garman@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