From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts (rev2)
Date: Tue, 29 Mar 2022 10:33:41 -0000 [thread overview]
Message-ID: <164855002154.5799.10036467121996367889@emeril.freedesktop.org> (raw)
In-Reply-To: <20220328172551.43309-1-matthew.auld@intel.com>
== Series Details ==
Series: series starting with [CI,1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts (rev2)
URL : https://patchwork.freedesktop.org/series/101899/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d7e2ab52888e drm/i915/gt: Explicitly clear BB_OFFSET for new contexts
6ae0170b05b0 drm/i915/selftests: Check for incomplete LRI from the context image
-:16: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16:
seen all the context registers by that point. (Mostly true for all gen so far,
total: 0 errors, 1 warnings, 0 checks, 121 lines checked
236d5c1ff105 drm/i915/selftest: Clear the output buffers before GPU writes
ce17ad9a6f22 drm/i915/selftest: Always cancel semaphore on error
next prev parent reply other threads:[~2022-03-29 10:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:25 [Intel-gfx] [CI 1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts Matthew Auld
2022-03-28 17:25 ` [Intel-gfx] [CI 2/4] drm/i915/selftests: Check for incomplete LRI from the context image Matthew Auld
2022-03-28 17:25 ` [Intel-gfx] [CI 3/4] drm/i915/selftest: Clear the output buffers before GPU writes Matthew Auld
2022-03-28 17:25 ` [Intel-gfx] [CI 4/4] drm/i915/selftest: Always cancel semaphore on error Matthew Auld
2022-03-29 0:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts Patchwork
2022-03-29 0:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-29 0:15 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-29 0:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29 3:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-29 7:50 ` [Intel-gfx] [CI 1/4] " Tvrtko Ursulin
2022-03-29 10:33 ` Patchwork [this message]
2022-03-29 10:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts (rev2) Patchwork
2022-03-29 10:38 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-29 11:16 ` [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=164855002154.5799.10036467121996367889@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.