public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Mahesh Kumar <mahesh1.kumar@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for CNL port refactoring
Date: Thu, 15 Feb 2018 10:01:58 -0000	[thread overview]
Message-ID: <20180215100158.20193.38321@emeril.freedesktop.org> (raw)
In-Reply-To: <20180215095643.3844-1-mahesh1.kumar@intel.com>

== Series Details ==

Series: CNL port refactoring
URL   : https://patchwork.freedesktop.org/series/38334/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
7464b147c8e2 drm/i915/cnl: Fix PORT_TX_DW5/7 register address
55e9964aae48 drm/i915/cnl; Add macro to get PORT_TX register
-:37: CHECK: spaces preferred around that '*' (ctx:VxV)
#37: FILE: drivers/gpu/drm/i915/i915_reg.h:1982:
+					       4*(dw))
 					        ^

-:45: CHECK: spaces preferred around that '*' (ctx:VxV)
#45: FILE: drivers/gpu/drm/i915/i915_reg.h:1990:
+					       4*(dw))
 					        ^

total: 0 errors, 0 warnings, 2 checks, 34 lines checked
29ca14f7c194 drm/i915/cnl: Replace PORT_TX register macros with new ones

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

  parent reply	other threads:[~2018-02-15 10:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15  9:56 [PATCH 0/3] CNL port refactoring Mahesh Kumar
2018-02-15  9:56 ` [PATCH 1/3] drm/i915/cnl: Fix PORT_TX_DW5/7 register address Mahesh Kumar
2018-02-15 14:02   ` Jani Nikula
2018-02-15 23:43     ` Rodrigo Vivi
2018-02-16 17:57       ` Rodrigo Vivi
2018-02-15  9:56 ` [PATCH 2/3] drm/i915/cnl; Add macro to get PORT_TX register Mahesh Kumar
2018-02-15  9:56 ` [PATCH 3/3] drm/i915/cnl: Replace PORT_TX register macros with new ones Mahesh Kumar
2018-02-15 10:01 ` Patchwork [this message]
2018-02-15 10:16 ` ✓ Fi.CI.BAT: success for CNL port refactoring 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=20180215100158.20193.38321@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mahesh1.kumar@intel.com \
    /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