From: Saul Wold <saul.wold@intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 0/1] Fix insane class ELF bitsize checks
Date: Thu, 03 Mar 2011 11:11:37 -0800 [thread overview]
Message-ID: <4D6FE7E9.7040709@intel.com> (raw)
In-Reply-To: <cover.1299005382.git.mark.hatle@windriver.com>
On 03/01/2011 10:50 AM, Mark Hatle wrote:
> The insane class was not checking the ELF bitsize, in fact if it wasn't
> correct it was skipping all of the QA checks!
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: mhatle/insane
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/insane
>
> Thanks,
> Mark Hatle<mark.hatle@windriver.com>
> ---
>
>
> Mark Hatle (1):
> insane.bbclass: Fix ELF bitsize comparison
>
> meta/classes/insane.bbclass | 84 ++++++++++++++++++++++---------------------
> meta/lib/oe/qa.py | 21 +++++++++--
> 2 files changed, 60 insertions(+), 45 deletions(-)
>
Merged into Bernard, OE-Core and Master
Thanks
Sau!
prev parent reply other threads:[~2011-03-03 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 18:50 [PATCH 0/1] Fix insane class ELF bitsize checks Mark Hatle
2011-03-01 18:50 ` [PATCH 1/1] insane.bbclass: Fix ELF bitsize comparison Mark Hatle
2011-03-03 19:11 ` Saul Wold [this message]
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=4D6FE7E9.7040709@intel.com \
--to=saul.wold@intel.com \
--cc=poky@yoctoproject.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