Intel-GFX Archive on 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: Remove partial attempt to swizzle on pread/pwrite
Date: Mon, 23 Jul 2018 09:49:50 -0000	[thread overview]
Message-ID: <20180723094950.14390.12130@emeril.freedesktop.org> (raw)
In-Reply-To: <20180723090208.27226-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Remove partial attempt to swizzle on pread/pwrite
URL   : https://patchwork.freedesktop.org/series/47043/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
f91f607dc2fa drm/i915: Remove partial attempt to swizzle on pread/pwrite
-:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#21: 
References: fe115628d567 ("drm/i915: Implement pwrite without struct-mutex")

-:21: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fe115628d567 ("drm/i915: Implement pwrite without struct-mutex")'
#21: 
References: fe115628d567 ("drm/i915: Implement pwrite without struct-mutex")

-:169: ERROR:SPACING: space prohibited after that '-' (ctx:WxW)
#169: FILE: drivers/gpu/drm/i915/i915_gem.c:1003:
+	return ret ? - EFAULT : 0;
 	             ^

total: 2 errors, 1 warnings, 0 checks, 270 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-23  9:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  9:02 [PATCH] drm/i915: Remove partial attempt to swizzle on pread/pwrite Chris Wilson
2018-07-23  9:11 ` Chris Wilson
2018-07-23  9:49 ` Patchwork [this message]
2018-07-23  9:50 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-07-23 10:12 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-10-11 13:38 ` [PATCH] " Tvrtko Ursulin
2018-10-11 14:30   ` Chris Wilson
2018-10-11 14:44     ` Tvrtko Ursulin
2018-10-12 11:56 ` [PATCH v3] " Chris Wilson
2018-10-12 12:22   ` Tvrtko Ursulin
2018-11-16 15:02   ` Joonas Lahtinen
2018-11-16 15:59     ` Kenneth Graunke
2018-10-12 12:21 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Remove partial attempt to swizzle on pread/pwrite (rev2) Patchwork
2018-10-12 12:21 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-10-12 12:46 ` ✗ Fi.CI.BAT: failure " 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=20180723094950.14390.12130@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