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 series starting with [1/6] drm/i915: Stop tracking timeline->inflight_seqnos
Date: Mon, 23 Apr 2018 13:24:27 -0000	[thread overview]
Message-ID: <20180423132427.5180.31492@emeril.freedesktop.org> (raw)
In-Reply-To: <20180423101400.27418-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/6] drm/i915: Stop tracking timeline->inflight_seqnos
URL   : https://patchwork.freedesktop.org/series/42111/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
cdd8eb08a9de drm/i915: Stop tracking timeline->inflight_seqnos
-:14: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 9b6586ae9f6b ("drm/i915: Keep a global seqno per-engine")'
#14: 
References: 9b6586ae9f6b ("drm/i915: Keep a global seqno per-engine")

total: 1 errors, 0 warnings, 0 checks, 67 lines checked
8456001c1d6e drm/i915: Retire requests along rings
7a4324010faa drm/i915: Only track live rings for retiring
c0197b0d3111 drm/i915: Move timeline from GTT to ring
13fe29e79460 drm/i915: Split i915_gem_timeline into individual timelines
-:447: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#447: 
deleted file mode 100644

-:948: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#948: FILE: drivers/gpu/drm/i915/i915_timeline.c:1:
+/*

total: 0 errors, 2 warnings, 0 checks, 1612 lines checked
2b96d52d778b drm/i915: Lazily unbind vma on close

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

  parent reply	other threads:[~2018-04-23 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 10:13 [PATCH 1/6] drm/i915: Stop tracking timeline->inflight_seqnos Chris Wilson
2018-04-23 10:13 ` [PATCH 2/6] drm/i915: Retire requests along rings Chris Wilson
2018-04-23 10:18   ` Tvrtko Ursulin
2018-04-23 10:13 ` [PATCH 3/6] drm/i915: Only track live rings for retiring Chris Wilson
2018-04-23 10:25   ` Tvrtko Ursulin
2018-04-23 10:36     ` Chris Wilson
2018-04-23 10:50       ` Tvrtko Ursulin
2018-04-23 10:13 ` [PATCH 4/6] drm/i915: Move timeline from GTT to ring Chris Wilson
2018-04-23 10:44   ` Tvrtko Ursulin
2018-04-23 12:51     ` Chris Wilson
2018-04-23 10:13 ` [PATCH 5/6] drm/i915: Split i915_gem_timeline into individual timelines Chris Wilson
2018-04-23 12:33   ` Tvrtko Ursulin
2018-04-23 12:55     ` Chris Wilson
2018-04-23 10:14 ` [PATCH 6/6] drm/i915: Lazily unbind vma on close Chris Wilson
2018-04-23 13:08   ` Tvrtko Ursulin
2018-04-23 13:24 ` Patchwork [this message]
2018-04-23 13:27 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/6] drm/i915: Stop tracking timeline->inflight_seqnos Patchwork
2018-04-23 13:40 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-04-23 13:49   ` Chris Wilson
2018-04-24 13:14 [PATCH 1/6] " Chris Wilson
2018-04-24 14:49 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] " 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=20180423132427.5180.31492@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.