From: Harish Chegondi <harish.chegondi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, petri.latvala@intel.com
Subject: [igt-dev] [PATCH i-g-t] runner/resultgen: Fix dmesg whitelist entry's regular expression
Date: Fri, 15 May 2020 00:41:50 -0700 [thread overview]
Message-ID: <20200515074150.475142-1-harish.chegondi@intel.com> (raw)
PCI devices' B/D/F numbers can have alphabets in hex. Fix the regexp
so that hex B/D/F numbers also match the regular expression.
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Swathi Dhanavanthri <swathi.dhanavanthri@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Signed-off-by: Harish Chegondi <harish.chegondi@intel.com>
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
runner/resultgen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/runner/resultgen.c b/runner/resultgen.c
index fe59aafeb..17147a8fa 100644
--- a/runner/resultgen.c
+++ b/runner/resultgen.c
@@ -800,7 +800,7 @@ static const char igt_dmesg_whitelist[] =
* module load after the testing finishes, which produces this
* message.
*/
- "i915: probe of [0-9:.]+ failed with error -25" _
+ "i915: probe of [0-9a-fA-F:.]+ failed with error -25" _
/* swiotbl warns even when asked not to */
"mock: DMA: Out of SW-IOMMU space for [0-9]+ bytes" _
"usb usb[0-9]+: root hub lost power or was reset"
--
2.25.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-05-15 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 7:41 Harish Chegondi [this message]
2020-05-15 9:21 ` [igt-dev] [PATCH i-g-t] runner/resultgen: Fix dmesg whitelist entry's regular expression Petri Latvala
2020-05-15 11:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-05-15 11:27 ` Petri Latvala
2020-05-15 13:19 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20200515074150.475142-1-harish.chegondi@intel.com \
--to=harish.chegondi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=petri.latvala@intel.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