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 drm/i915/execlists: Leave resetting ring to intel_ring
Date: Wed, 15 Jan 2020 18:11:20 -0000 [thread overview]
Message-ID: <157911188090.2008.11168323748384081956@emeril.freedesktop.org> (raw)
In-Reply-To: <20200115175829.2761329-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915/execlists: Leave resetting ring to intel_ring
URL : https://patchwork.freedesktop.org/series/72082/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d1f45157e453 drm/i915/execlists: Leave resetting ring to intel_ring
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
References: 0725d9a31869 ("drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint")
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0725d9a31869 ("drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint")'
#14:
References: 0725d9a31869 ("drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint")
total: 1 errors, 1 warnings, 0 checks, 7 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:[~2020-01-15 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 17:58 [Intel-gfx] [PATCH] drm/i915/execlists: Leave resetting ring to intel_ring Chris Wilson
2020-01-15 18:11 ` Patchwork [this message]
2020-01-15 18:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-15 18:51 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-16 12:34 ` [Intel-gfx] [PATCH] " Mika Kuoppala
2020-01-18 6:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=157911188090.2008.11168323748384081956@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).