All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "John Harrison" <john.c.harrison@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Random assortment of (mostly) GuC related patches (rev3)
Date: Thu, 28 Jul 2022 03:09:49 -0000	[thread overview]
Message-ID: <165897778977.21234.16583848674198790852@emeril.freedesktop.org> (raw)
In-Reply-To: <20220728024225.2363663-1-John.C.Harrison@Intel.com>

== Series Details ==

Series: Random assortment of (mostly) GuC related patches (rev3)
URL   : https://patchwork.freedesktop.org/series/106272/
State : warning

== Summary ==

Error: dim checkpatch failed
fe6417b35380 drm/i915/guc: Route semaphores to GuC for Gen12+
383e87c640b2 drm/i915/guc: Fix issues with live_preempt_cancel
e13f86d5e8df drm/i915/guc: Add selftest for a hung GuC
Traceback (most recent call last):
  File "scripts/spdxcheck.py", line 11, in <module>
    import git
ModuleNotFoundError: No module named 'git'
-:23: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#23: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 170 lines checked
62827ece554d drm/i915/selftest: Cope with not having an RCS engine
d91bb3719581 drm/i915/guc: Support larger contexts on newer hardware
d0928d5d4461 drm/i915/guc: Don't abort on CTB_UNUSED status



  parent reply	other threads:[~2022-07-28  3:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  2:42 [PATCH 0/6] Random assortment of (mostly) GuC related patches John.C.Harrison
2022-07-28  2:42 ` [Intel-gfx] " John.C.Harrison
2022-07-28  2:42 ` [PATCH 1/6] drm/i915/guc: Route semaphores to GuC for Gen12+ John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28  2:42 ` [PATCH 2/6] drm/i915/guc: Fix issues with live_preempt_cancel John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28  2:45   ` John Harrison
2022-07-28  2:45     ` [Intel-gfx] " John Harrison
2022-07-28  2:42 ` [PATCH 3/6] drm/i915/guc: Add selftest for a hung GuC John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28 18:21   ` John Harrison
2022-07-28 18:21     ` [Intel-gfx] " John Harrison
2022-07-28 18:26     ` John.C.Harrison
2022-07-28 18:26       ` [Intel-gfx] " John.C.Harrison
2022-07-28 18:33       ` John Harrison
2022-07-28 18:33         ` [Intel-gfx] " John Harrison
2022-07-28  2:42 ` [PATCH 4/6] drm/i915/selftest: Cope with not having an RCS engine John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28  2:42 ` [PATCH 5/6] drm/i915/guc: Support larger contexts on newer hardware John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28  2:46   ` John Harrison
2022-07-28  2:46     ` [Intel-gfx] " John Harrison
2022-07-28  2:42 ` [PATCH 6/6] drm/i915/guc: Don't abort on CTB_UNUSED status John.C.Harrison
2022-07-28  2:42   ` [Intel-gfx] " John.C.Harrison
2022-07-28 19:06   ` Michal Wajdeczko
2022-07-28 19:38     ` John Harrison
2022-07-29  0:00   ` Ceraolo Spurio, Daniele
2022-07-29  0:35     ` John Harrison
2022-07-28  3:09 ` Patchwork [this message]
2022-07-28  3:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Random assortment of (mostly) GuC related patches (rev3) Patchwork
2022-07-28  3:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-28 10:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-07-28 19:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Random assortment of (mostly) GuC related patches (rev4) Patchwork
2022-07-28 19:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-07-28 19:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-07-29  0:40   ` John Harrison

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=165897778977.21234.16583848674198790852@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@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.