From: Patchwork <patchwork@emeril.freedesktop.org>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BUILD: failure for tests/core_hotunplug: New subtests and enhancements
Date: Mon, 22 Jun 2020 15:41:25 -0000 [thread overview]
Message-ID: <159284048580.9207.12451473549257982443@emeril.freedesktop.org> (raw)
In-Reply-To: <20200622151845.4520-1-janusz.krzysztofik@linux.intel.com>
== Series Details ==
Series: tests/core_hotunplug: New subtests and enhancements
URL : https://patchwork.freedesktop.org/series/78698/
State : failure
== Summary ==
Applying: tests/core_hotunplug: Duplicate debug messages in dmesg
Applying: tests/core_hotunplug: Use PCI device sysfs entry, not DRM
Applying: tests/core_hotunplug: Add unbind-unplug-rescan variant
Applying: tests/core_hotunplug: Add 'lateclose before recover' variants
Applying: tests/core_hotunplug: Add 'GEM address space' variant
Applying: tests/core_hotunplug: Add 'GEM object' variant
Applying: tests/core_hotunplug: Add 'PRIME handle' variant
Applying: tests/core_hotunplug: Add 'GEM batch' variant
Patch failed at 0008 tests/core_hotunplug: Add 'GEM batch' variant
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2020-06-22 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 15:18 [Intel-gfx] [RFC PATCH i-g-t 0/8] tests/core_hotunplug: New subtests and enhancements Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 1/8] tests/core_hotunplug: Duplicate debug messages in dmesg Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 2/8] tests/core_hotunplug: Use PCI device sysfs entry, not DRM Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 3/8] tests/core_hotunplug: Add unbind-unplug-rescan variant Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 4/8] tests/core_hotunplug: Add 'lateclose before recover' variants Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 5/8] tests/core_hotunplug: Add 'GEM address space' variant Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 6/8] tests/core_hotunplug: Add 'GEM object' variant Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 7/8] tests/core_hotunplug: Add 'PRIME handle' variant Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:18 ` [Intel-gfx] [RFC PATCH i-g-t 8/8] tests/core_hotunplug: Add 'GEM batch' variant Janusz Krzysztofik
2020-06-22 15:18 ` [igt-dev] " Janusz Krzysztofik
2020-06-22 15:41 ` Patchwork [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=159284048580.9207.12451473549257982443@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.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 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.