Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org, akuster@mvista.com
Subject: [PATCH 0/6] Krogoth pull request
Date: Wed,  6 Jul 2016 08:04:10 -0700	[thread overview]
Message-ID: <cover.1467816214.git.akuster808@gmail.com> (raw)

Here are a few more changes for krogoth-next. The first two are the ones we talked about in the YPTM. The rest are bonus.


The following changes since commit 7e9297e5722d0a589fae1158908cf8cf8c1d0b37:

  bitbake: bitbake: fetch2: Safer check for BB_ORIGENV datastore (2016-06-28 15:22:59 -0700)

are available in the git repository at:

  http://git.yoctoproject.org/git/poky-contrib akuster/krogoth-next
  http://git.yoctoproject.org/cgit.cgi//log/?h=akuster/krogoth-next

André Draszik (1):
  feature-arm-vfp.inc: fix overzealous ARMPKGSFX_FPU modification

Anuj Mittal (1):
  gcc: make sure header path is set correctly

Armin Kuster (1):
  Revert "openssl: prevent ABI break from earlier krogoth releases"

Ed Bartosh (2):
  devshell.bbclass: fix double unbuffering
  wic: rawcopy: make source filenames unique

Khem Raj (1):
  gcc-5: Fix hang with mmusl option on cmdline

 meta/classes/devshell.bbclass                      |  1 -
 meta/conf/machine/include/arm/feature-arm-vfp.inc  |  2 +-
 .../openssl/debian1.0.2/version-script.patch       | 31 +++-------
 ...l-as-a-musl-libc-specifier-and-the-necess.patch | 72 +++++++++++-----------
 meta/recipes-devtools/gcc/gcc-target.inc           |  1 -
 scripts/lib/wic/plugins/source/rawcopy.py          |  2 +-
 6 files changed, 47 insertions(+), 62 deletions(-)

-- 
1.9.1



                 reply	other threads:[~2016-07-06 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1467816214.git.akuster808@gmail.com \
    --to=akuster808@gmail.com \
    --cc=akuster@mvista.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