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, saul.wold@intel.com
Subject: [PATCH 0/2] linux-yocto: custom repo fixes
Date: Thu, 23 Aug 2012 00:08:43 -0400	[thread overview]
Message-ID: <cover.1345694632.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

I worked through some custom repository issues over the past day, and
the outcome is two small patches to fix some corner cases. I've tested
these with the standard linux-yocto recipes, with my base linux-yocto-custom,
eternalsrc and the repositories that were showing the error.

(patches are stacked on my yocto base, but that history has no impact).

Cheers,

Bruce

The following changes since commit 19ff55a53b436d463f9577adaed15be77708f0d2:

  routerstationpro: move board off 3.0 and onto the 3.4 kernel (2012-08-22 14:26:10 +0100)

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 (2):
  kernel-yocto: don't require meta branch for custom repos
  kernel-yocto: set master branch to a defined SRCREV

 meta/classes/kernel-yocto.bbclass                  |   17 +++++++++++------
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 2 files changed, 12 insertions(+), 7 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-08-23  4:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23  4:08 Bruce Ashfield [this message]
2012-08-23  4:08 ` [PATCH 1/2] kernel-yocto: don't require meta branch for custom repos Bruce Ashfield
2012-08-23  4:08 ` [PATCH 2/2] kernel-yocto: set master branch to a defined SRCREV Bruce Ashfield
2012-08-27 15:42 ` [PATCH 0/2] linux-yocto: custom repo 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.1345694632.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.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 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.