From: Saul Wold <saul.wold@intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Subject: Re: [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues
Date: Mon, 21 Mar 2016 18:50:56 -0700 [thread overview]
Message-ID: <1458611456.5327.25.camel@intel.com> (raw)
In-Reply-To: <1458336286-21607-1-git-send-email-sgw@linux.intel.com>
Did this v2 get missed? I see the first patch got merged.
Sau!
On Fri, 2016-03-18 at 14:24 -0700, Saul Wold wrote:
> Adds intel-corei7-64 with x86-common, this makes the x86-common
> whitelist available for intel-corei7-64 bsp also.
>
> [YOCTO #9179]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/lib/oeqa/runtime/parselogs.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/lib/oeqa/runtime/parselogs.py
> b/meta/lib/oeqa/runtime/parselogs.py
> index 431c436..4def533 100644
> --- a/meta/lib/oeqa/runtime/parselogs.py
> +++ b/meta/lib/oeqa/runtime/parselogs.py
> @@ -54,6 +54,7 @@ x86_common = [
> 'wrong ELF class',
> 'Could not enable PowerButton event',
> 'probe of LNXPWRBN:00 failed with error -22',
> + 'pmd_set_huge: Cannot satisfy',
> ] + common_errors
>
> qemux86_common = [
> @@ -110,6 +111,7 @@ ignore_errors = {
> '(EE) open /dev/fb0: No such file or directory',
> '(EE) AIGLX: reverting to software rendering',
> ] + x86_common,
> + 'intel-corei7-64' : x86_common,
> 'crownbay' : x86_common,
> 'genericx86' : x86_common,
> 'genericx86-64' : x86_common,
> --
> 2.5.0
>
next prev parent reply other threads:[~2016-03-22 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 21:24 [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues Saul Wold
2016-03-22 1:50 ` Saul Wold [this message]
2016-03-22 8:57 ` 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=1458611456.5327.25.camel@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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