From: Patchwork <patchwork@emeril.freedesktop.org>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for GuC fixes (rev2)
Date: Wed, 22 May 2019 20:34:17 -0000 [thread overview]
Message-ID: <20190522203417.10330.32288@emeril.freedesktop.org> (raw)
In-Reply-To: <20190522193203.23932-1-michal.wajdeczko@intel.com>
== Series Details ==
Series: GuC fixes (rev2)
URL : https://patchwork.freedesktop.org/series/60795/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
54ff1dca4c58 drm/i915/selftests: Move some reset testcases to separate file
-:95: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#95:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 152 lines checked
010025dfb682 drm/i915/selftests: Split igt_atomic_reset testcase
-:233: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#233: FILE: drivers/gpu/drm/i915/gt/selftest_reset.c:82:
+ pr_err("intel_gpu_reset failed under %s\n",
+ p->name);
-:258: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#258:
new file mode 100644
total: 0 errors, 1 warnings, 1 checks, 299 lines checked
a24312534312 drm/i915/selftests: Use prepare/finish during atomic reset test
346a854fbd49 drm/i915/guc: Rename intel_guc_is_alive to intel_guc_is_loaded
6a0e54a07d39 drm/i915/uc: Explicitly sanitize GuC/HuC on failure and finish
599cfb7e0a02 drm/i915/uc: Use GuC firmware status helper
cea15b131008 drm/i915/uc: Skip GuC HW unwinding if GuC is already dead
191f064b4da3 drm/i915/uc: Stop talking with GuC when resetting
df2d1b431445 drm/i915/uc: Skip reset preparation if GuC is already dead
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-22 20:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:31 [PATCH v2 0/9] GuC fixes Michal Wajdeczko
2019-05-22 19:31 ` [PATCH v2 1/9] drm/i915/selftests: Move some reset testcases to separate file Michal Wajdeczko
2019-05-22 19:53 ` Chris Wilson
2019-05-22 19:31 ` [PATCH v2 2/9] drm/i915/selftests: Split igt_atomic_reset testcase Michal Wajdeczko
2019-05-22 19:55 ` Chris Wilson
2019-05-22 19:31 ` [PATCH v2 3/9] drm/i915/selftests: Use prepare/finish during atomic reset test Michal Wajdeczko
2019-05-22 19:56 ` Chris Wilson
2019-05-22 19:31 ` [PATCH v2 4/9] drm/i915/guc: Rename intel_guc_is_alive to intel_guc_is_loaded Michal Wajdeczko
2019-05-22 19:56 ` Chris Wilson
2019-05-22 19:31 ` [PATCH v2 5/9] drm/i915/uc: Explicitly sanitize GuC/HuC on failure and finish Michal Wajdeczko
2019-05-22 19:58 ` Chris Wilson
2019-05-22 19:32 ` [PATCH v2 6/9] drm/i915/uc: Use GuC firmware status helper Michal Wajdeczko
2019-05-22 19:58 ` Chris Wilson
2019-05-22 19:32 ` [PATCH v2 7/9] drm/i915/uc: Skip GuC HW unwinding if GuC is already dead Michal Wajdeczko
2019-05-22 19:59 ` Chris Wilson
2019-05-22 19:32 ` [PATCH v2 8/9] drm/i915/uc: Stop talking with GuC when resetting Michal Wajdeczko
2019-05-22 20:06 ` Chris Wilson
2019-05-23 15:53 ` Michal Wajdeczko
2019-05-23 16:08 ` Chris Wilson
2019-05-23 17:25 ` Michal Wajdeczko
2019-05-23 20:50 ` Chris Wilson
2019-05-22 19:32 ` [PATCH v2 9/9] drm/i915/uc: Skip reset preparation if GuC is already dead Michal Wajdeczko
2019-05-22 20:04 ` Chris Wilson
2019-05-22 20:34 ` Patchwork [this message]
2019-05-22 20:53 ` ✗ Fi.CI.BAT: failure for GuC fixes (rev2) Patchwork
2019-05-23 14:46 ` Michal Wajdeczko
2019-05-23 20:58 ` Chris Wilson
2019-05-23 17:40 ` ✗ Fi.CI.CHECKPATCH: warning for GuC fixes (rev3) Patchwork
2019-05-23 18:39 ` ✗ Fi.CI.BAT: failure " 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=20190522203417.10330.32288@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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;
as well as URLs for NNTP newsgroup(s).