All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Abdiel Janulgue" <abdiel.janulgue@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add lmem fault handler (rev2)
Date: Wed, 11 Dec 2019 07:40:08 -0000	[thread overview]
Message-ID: <157605000877.30694.14703520167409153805@emeril.freedesktop.org> (raw)
In-Reply-To: <20191211055907.8398-1-abdiel.janulgue@linux.intel.com>

== Series Details ==

Series: drm/i915: Add lmem fault handler (rev2)
URL   : https://patchwork.freedesktop.org/series/70485/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
391e63451f37 drm/i915: Add lmem fault handler
-:151: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#151: FILE: drivers/gpu/drm/i915/gem/i915_gem_mman.c:701:
+       .fault = vm_fault_lmem,$

-:152: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#152: FILE: drivers/gpu/drm/i915/gem/i915_gem_mman.c:702:
+       .open = vm_open,$

-:153: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#153: FILE: drivers/gpu/drm/i915/gem/i915_gem_mman.c:703:
+       .close = vm_close,$

total: 0 errors, 3 warnings, 0 checks, 301 lines checked

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

  reply	other threads:[~2019-12-11  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  5:59 [Intel-gfx] [PATCH] drm/i915: Add lmem fault handler Abdiel Janulgue
2019-12-11  7:40 ` Patchwork [this message]
2019-12-11  8:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Add lmem fault handler (rev2) Patchwork
2019-12-11  9:39 ` [Intel-gfx] [PATCH] drm/i915: Add lmem fault handler Chris Wilson
2019-12-11 15:29 ` Chris Wilson
2019-12-13  9:49 ` Dan Carpenter
2019-12-13  9:49   ` Dan Carpenter
2019-12-13  9:49   ` Dan Carpenter

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=157605000877.30694.14703520167409153805@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=abdiel.janulgue@linux.intel.com \
    --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.