All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petter Mabäcker" <petter@technux.se>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] x-load: fix broken beaglebone support and FILEPATHS usage
Date: Sat, 26 Apr 2014 00:11:12 +0200	[thread overview]
Message-ID: <cover.1398462168.git.petter@technux.se> (raw)

The following changes since commit c446d4edca3b4edfcdee48247391bfb306aab4c2:

  default-distrovars.inc: Add libgcc-initial to the GPLv3 whitelist (same as libgcc) (2014-04-25 18:00:38 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib petmab/fix_xload
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/fix_xload

Petter Mabäcker (2):
  x-load: fix broken beaglebone support
  x-load: remove usage of FILESPATH

 .../x-load/x-load-git/beagleboard/name.patch       |   18 ----------
 .../0001-Change-omap3530beagle-target-name.patch   |   37 ++++++++++++++++++++
 meta/recipes-bsp/x-load/x-load_git.bb              |    6 ++--
 3 files changed, 39 insertions(+), 22 deletions(-)
 delete mode 100644 meta/recipes-bsp/x-load/x-load-git/beagleboard/name.patch
 create mode 100644 meta/recipes-bsp/x-load/x-load/beaglebone/0001-Change-omap3530beagle-target-name.patch

-- 
1.7.9.5



             reply	other threads:[~2014-04-25 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 22:11 Petter Mabäcker [this message]
2014-04-25 22:11 ` [PATCH 1/2] x-load: fix broken beaglebone support Petter Mabäcker
2014-04-25 22:11 ` [PATCH 2/2] x-load: remove usage of FILESPATH Petter Mabäcker
2014-04-26 13:10 ` [PATCH 0/2] x-load: fix broken beaglebone support and FILEPATHS usage Gary Thomas
2014-04-26 18:39   ` petter
2014-04-27  9:52     ` Koen Kooi
2014-04-27 11:22       ` petter

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.1398462168.git.petter@technux.se \
    --to=petter@technux.se \
    --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 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.