From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: Move GGTT fence registers under gt/
Date: Mon, 16 Mar 2020 15:47:37 -0000 [thread overview]
Message-ID: <158437365733.18996.9784634310240835389@emeril.freedesktop.org> (raw)
In-Reply-To: <20200314122058.21472-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/7] drm/i915: Move GGTT fence registers under gt/
URL : https://patchwork.freedesktop.org/series/74703/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cfd159dc30dd drm/i915: Move GGTT fence registers under gt/
-:6: WARNING:TYPO_SPELLING: 'throught' may be misspelled - perhaps 'through'?
#6:
Since the fence registers control HW detiling throught the GGTT
-:47: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#47:
rename from drivers/gpu/drm/i915/i915_gem_fence_reg.c
total: 0 errors, 2 warnings, 0 checks, 205 lines checked
4e7c950ab87c drm/i915/gt: Pull restoration of GGTT fences underneath the GT
84d01acc1bc9 drm/i915: Remove manual save/resume of fence register state
9f9e340e8b4d drm/i915/gt: Allocate i915_fence_reg array
5003f815b7aa drm/i915/gt: Store the fence details on the fence
750dc9e7ceb3 drm/i915/gt: Only wait for GPU activity before unbinding a GGTT fence
9eeea4468363 drm/i915/gt: Make fence revocation unequivocal
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-16 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 12:20 [Intel-gfx] [PATCH 1/7] drm/i915: Move GGTT fence registers under gt/ Chris Wilson
2020-03-14 12:20 ` [Intel-gfx] [PATCH 2/7] drm/i915/gt: Pull restoration of GGTT fences underneath the GT Chris Wilson
2020-03-14 12:20 ` [Intel-gfx] [PATCH 3/7] drm/i915: Remove manual save/resume of fence register state Chris Wilson
2020-03-16 7:14 ` Mika Kuoppala
2020-03-14 12:20 ` [Intel-gfx] [PATCH 4/7] drm/i915/gt: Allocate i915_fence_reg array Chris Wilson
2020-03-16 7:29 ` Mika Kuoppala
2020-03-16 10:23 ` Chris Wilson
2020-03-16 11:20 ` Mika Kuoppala
2020-03-14 12:20 ` [Intel-gfx] [PATCH 5/7] drm/i915/gt: Store the fence details on the fence Chris Wilson
2020-03-14 12:20 ` [Intel-gfx] [PATCH 6/7] drm/i915/gt: Only wait for GPU activity before unbinding a GGTT fence Chris Wilson
2020-03-14 12:20 ` [Intel-gfx] [PATCH 7/7] drm/i915/gt: Make fence revocation unequivocal Chris Wilson
2020-03-16 7:02 ` [Intel-gfx] [PATCH 1/7] drm/i915: Move GGTT fence registers under gt/ Mika Kuoppala
2020-03-16 15:47 ` Patchwork [this message]
2020-03-16 16:06 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/7] " Patchwork
2020-03-16 16:17 ` [Intel-gfx] ✗ 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=158437365733.18996.9784634310240835389@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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).