* [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues
@ 2016-03-18 21:24 Saul Wold
2016-03-22 1:50 ` Saul Wold
0 siblings, 1 reply; 3+ messages in thread
From: Saul Wold @ 2016-03-18 21:24 UTC (permalink / raw)
To: openembedded-core, richard.purdie
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues
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
2016-03-22 8:57 ` Richard Purdie
0 siblings, 1 reply; 3+ messages in thread
From: Saul Wold @ 2016-03-22 1:50 UTC (permalink / raw)
To: openembedded-core, richard.purdie
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues
2016-03-22 1:50 ` Saul Wold
@ 2016-03-22 8:57 ` Richard Purdie
0 siblings, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2016-03-22 8:57 UTC (permalink / raw)
To: Saul Wold, openembedded-core
On Mon, 2016-03-21 at 18:50 -0700, Saul Wold wrote:
> Did this v2 get missed? I see the first patch got merged.
Clearly it got missed sorry.
I appreciate that is frustrating for people, equally, we do some level
of testing of changes going in, which introduces delay and when you
have ~80 patches you're about to merge and scan the lists for new
versions, its sometimes hard to catch everything :(.
Its also even harder when the v2 is buried in some random git branch
somewhere which I appreciate in this case it wasn't but does cause
problems in general.
Cheers,
Richard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-03-22 8:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2016-03-22 8:57 ` Richard Purdie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.