From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross@burtonini.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] lib/oe/qa: handle the 'no specific instruction set' ELF e_machine value
Date: Sat, 19 Dec 2020 11:26:41 +0000 [thread overview]
Message-ID: <b73183a95db599853ce42b84702c694748af5310.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201218144335.1189805-1-ross.burton@arm.com>
On Fri, 2020-12-18 at 14:43 +0000, Ross Burton wrote:
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> meta/lib/oe/qa.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/lib/oe/qa.py b/meta/lib/oe/qa.py
> index ea831b930a..e8a854a302 100644
> --- a/meta/lib/oe/qa.py
> +++ b/meta/lib/oe/qa.py
> @@ -156,6 +156,7 @@ def elf_machine_to_string(machine):
> """
> try:
> return {
> + 0x00: "Unset",
> 0x02: "SPARC",
> 0x03: "x86",
> 0x08: "MIPS",
This breaks the selftests that lib/oe/qa.py has. I'll fix it up.
Cheers,
Richard
prev parent reply other threads:[~2020-12-19 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 14:43 [PATCH] lib/oe/qa: handle the 'no specific instruction set' ELF e_machine value Ross Burton
2020-12-19 11:26 ` Richard Purdie [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=b73183a95db599853ce42b84702c694748af5310.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox