From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ringbuffer: Move double invalidate to after pd flush
Date: Tue, 04 Sep 2018 06:45:04 -0000 [thread overview]
Message-ID: <20180904064504.7482.96271@emeril.freedesktop.org> (raw)
In-Reply-To: <20180904063802.13880-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/ringbuffer: Move double invalidate to after pd flush
URL : https://patchwork.freedesktop.org/series/49104/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
fd054884982c drm/i915/ringbuffer: Move double invalidate to after pd flush
-:15: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#15:
References: 70b73f9ac113 ("drm/i915/ringbuffer: Delay after invalidating gen6+ xcs")
-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 70b73f9ac113 ("drm/i915/ringbuffer: Delay after invalidating gen6+ xcs")'
#15:
References: 70b73f9ac113 ("drm/i915/ringbuffer: Delay after invalidating gen6+ xcs")
total: 1 errors, 1 warnings, 0 checks, 61 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-04 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 6:38 [PATCH] drm/i915/ringbuffer: Move double invalidate to after pd flush Chris Wilson
2018-09-04 6:45 ` Patchwork [this message]
2018-09-04 7:03 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-09-04 8:21 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-04 13:22 ` [PATCH] " Mika Kuoppala
2018-09-04 13:27 ` Chris Wilson
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=20180904064504.7482.96271@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