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: Use b->irq_enable() as predicate for mock engine
Date: Fri, 18 Jan 2019 11:33:22 -0000	[thread overview]
Message-ID: <20190118113322.22164.62225@emeril.freedesktop.org> (raw)
In-Reply-To: <20190118112225.13780-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Use b->irq_enable() as predicate for mock engine
URL   : https://patchwork.freedesktop.org/series/55402/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
10d3f2b41159 drm/i915: Use b->irq_enable() as predicate for mock engine
-:6: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d4ccceb05591 ("drm/i915/icl: Ringbuffer interrupt handling")'
#6: 
Since commit  d4ccceb05591 ("drm/i915/icl: Ringbuffer interrupt handling")

-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d4ccceb05591 ("drm/i915/icl: Ringbuffer interrupt handling")'
#15: 
References: d4ccceb05591 ("drm/i915/icl: Ringbuffer interrupt handling")

total: 2 errors, 0 warnings, 0 checks, 72 lines checked

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

  reply	other threads:[~2019-01-18 11:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 11:22 [CI] drm/i915: Use b->irq_enable() as predicate for mock engine Chris Wilson
2019-01-18 11:33 ` Patchwork [this message]
2019-01-18 11:59 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-18 17:37 ` ✓ Fi.CI.IGT: " 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=20190118113322.22164.62225@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.