All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto/meta-yocto: update hardware reference SRCREVs
Date: Fri, 13 Apr 2012 16:40:30 -0400	[thread overview]
Message-ID: <cover.1334349467.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

When I bumped the reference boards to v3.0.34 a merge commit was missed.
This wasn't immediately visible since for most boards, it didn't matter,
and for the one that it did .. the board built fine:

Here's the patch commit header repeated:

[
  commit 8cd31f9b0 linux-yocto/meta-yocto: update hardware reference boards to v3.0.24

  Missed a merge commit on the hardware reference BSP branches.

  As a result, validate_branches is adjusting the tree to build the
  proper SRCREV. For machines with board specific commits this means
  that some of their commits are missing, which leads to boot failure.

  Bumping the SRCREVs fixes the problem
]

Fixes [YOCTO: #2292]

Cheers,

Bruce


The following changes since commit 04b16f1038f7cae445d741e86c2cc19c70f991c1:

  rpm-native: Compile python rpm module (with-python) (2012-04-13 16:04:12 +0100)

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

Bruce Ashfield (1):
  linux-yocto/meta-yocto: update hardware reference SRCREVs

 .../recipes-kernel/linux/linux-yocto_3.0.bbappend  |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

-- 
1.7.5.4



             reply	other threads:[~2012-04-13 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 20:40 Bruce Ashfield [this message]
2012-04-13 20:40 ` [PATCH 1/1] linux-yocto/meta-yocto: update hardware reference SRCREVs Bruce Ashfield
2012-04-13 22:15 ` [PATCH 0/1] " 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.1334349467.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.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 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.