From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Two minor fixes for oe-core
Date: Thu, 3 Mar 2011 10:47:29 -0600 [thread overview]
Message-ID: <cover.1299170758.git.mark.hatle@windriver.com> (raw)
The first fix implementes the workaround I posted in the oe-core getting
started. Simply adding the BBFETCH2=True is all that is needed.
The second fixes the ELF qa loaders bit size identification.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: mhatle/oecore/fixes
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/oecore/fixes
Thanks,
Mark Hatle <mark.hatle@windriver.com>
---
Mark Hatle (2):
poky-env-internal: Add FETCH2 enablement
qa.py: Fix a typo when evaluating bitsize
meta/lib/oe/qa.py | 4 ++--
scripts/poky-env-internal | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
--
1.7.4
next reply other threads:[~2011-03-03 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 16:47 Mark Hatle [this message]
2011-03-03 16:47 ` [PATCH 1/2] poky-env-internal: Add FETCH2 enablement Mark Hatle
2011-03-03 16:47 ` [PATCH 2/2] qa.py: Fix a typo when evaluating bitsize Mark Hatle
2011-03-03 23:29 ` [PATCH 0/2] Two minor fixes for oe-core 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.1299170758.git.mark.hatle@windriver.com \
--to=mark.hatle@windriver.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