All of lore.kernel.org
 help / color / mirror / Atom feed
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: Allow i915_gem_reset_prepare_engine to recurse
Date: Mon, 14 May 2018 21:58:31 -0000	[thread overview]
Message-ID: <20180514215831.18100.7682@emeril.freedesktop.org> (raw)
In-Reply-To: <20180514205213.31017-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Allow i915_gem_reset_prepare_engine to recurse
URL   : https://patchwork.freedesktop.org/series/43156/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
7fae27664969 drm/i915: Allow i915_gem_reset_prepare_engine to recurse
-:57: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#57: 
References: 85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue")

-:57: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue")'
#57: 
References: 85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue")

-:173: CHECK:UNCOMMENTED_DEFINITION: struct mutex definition without comment
#173: FILE: drivers/gpu/drm/i915/intel_ringbuffer.h:569:
+	struct mutex reset_lock;

total: 1 errors, 1 warnings, 1 checks, 99 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-05-14 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 20:52 [PATCH] drm/i915: Allow i915_gem_reset_prepare_engine to recurse Chris Wilson
2018-05-14 21:08 ` Chris Wilson
2018-05-14 21:58 ` Patchwork [this message]
2018-05-14 22:08 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-05-15  8:08 ` [PATCH] " Mika Kuoppala
2018-05-15  8:13   ` 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=20180514215831.18100.7682@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 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.