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: Clean up ancient doc comments for i915_ioc32.c
Date: Wed, 14 Feb 2018 15:45:55 -0000	[thread overview]
Message-ID: <20180214154555.21135.36030@emeril.freedesktop.org> (raw)
In-Reply-To: <20180214152911.9242-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915: Clean up ancient doc comments for i915_ioc32.c
URL   : https://patchwork.freedesktop.org/series/38261/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
7363afa51c03 drm/i915: Clean up ancient doc comments for i915_ioc32.c
-:52: CHECK: Alignment should match open parenthesis
#52: FILE: drivers/gpu/drm/i915/i915_ioc32.c:58:
+	    __put_user((void __user *)(unsigned long)req32.value,
 			  &request->value))

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

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

  parent reply	other threads:[~2018-02-14 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:29 [PATCH] drm/i915: Clean up ancient doc comments for i915_ioc32.c Chris Wilson
2018-02-14 15:42 ` Jani Nikula
2018-02-14 15:47   ` Chris Wilson
2018-02-14 16:09     ` Jani Nikula
2018-02-14 15:45 ` Patchwork [this message]
2018-02-14 16:01 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-14 16:05 ` [PATCH v2] " Chris Wilson
2018-02-14 16:07 ` [PATCH v3] " Chris Wilson
2018-02-15  7:43   ` Chris Wilson
2018-02-15 14:00     ` Jani Nikula
2018-02-15 17:05       ` Chris Wilson
2018-02-14 17:36 ` ✓ Fi.CI.BAT: success for drm/i915: Clean up ancient doc comments for i915_ioc32.c (rev3) Patchwork
2018-02-15  0:27 ` ✓ 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=20180214154555.21135.36030@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.