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: Refactor export_fence() after i915_vma_move_to_active() (rev2)
Date: Fri, 06 Jul 2018 15:05:39 -0000	[thread overview]
Message-ID: <20180706150539.22154.90742@emeril.freedesktop.org> (raw)
In-Reply-To: <20180706103947.15919-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)
URL   : https://patchwork.freedesktop.org/series/46067/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
c404016bcc1d drm/i915: Refactor export_fence() after i915_vma_move_to_active()
951d50a80f49 drm/i915: Export i915_request_skip()
39fbb254f607 drm/i915: Start returning an error from i915_vma_move_to_active()
78318c338989 drm/i915: Move i915_vma_move_to_active() to i915_vma.c
42d0e21316dd drm/i915: Track vma activity per fence.context, not per engine
a65a91a8871c drm/i915: Track the last-active inside the i915_vma
-:97: WARNING:TYPO_SPELLING: 'recieve' may be misspelled - perhaps 'receive'?
#97: FILE: drivers/gpu/drm/i915/i915_vma.c:959:
+	 * we must be careful as we now only expect to recieve one retire

total: 0 errors, 1 warnings, 0 checks, 101 lines checked

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

  parent reply	other threads:[~2018-07-06 15:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 10:39 [PATCH 1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-07-06 10:39 ` [PATCH 2/6] drm/i915: Export i915_request_skip() Chris Wilson
2018-07-06 10:39 ` [PATCH 3/6] drm/i915: Start returning an error from i915_vma_move_to_active() Chris Wilson
2018-07-06 10:39 ` [PATCH 4/6] drm/i915: Move i915_vma_move_to_active() to i915_vma.c Chris Wilson
2018-07-06 10:39 ` [PATCH 5/6] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-07-06 10:39 ` [PATCH 6/6] drm/i915: Track the last-active inside the i915_vma Chris Wilson
2018-07-06 11:07   ` Tvrtko Ursulin
2018-07-06 12:31   ` [PATCH v5] " Chris Wilson
2018-07-06 12:02 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Patchwork
2018-07-06 12:05 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-06 12:20 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-07-06 12:25   ` Chris Wilson
2018-07-06 15:05 ` Patchwork [this message]
2018-07-06 15:08 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) Patchwork
2018-07-06 15:21 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-07 11:30 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2018-06-29 22:54 [PATCH 1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-07-04  8:52 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) 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=20180706150539.22154.90742@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.