public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm: PATH prop for all connectors?
Date: Thu, 13 Jun 2019 18:50:17 -0000	[thread overview]
Message-ID: <20190613185017.17470.75628@emeril.freedesktop.org> (raw)
In-Reply-To: <20190613184335.7970-1-ville.syrjala@linux.intel.com>

== Series Details ==

Series: drm: PATH prop for all connectors?
URL   : https://patchwork.freedesktop.org/series/62061/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
e51dfaa72985 drm: Improve PATH prop docs
-:30: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#30: FILE: drivers/gpu/drm/drm_connector.c:898:
+ * ^Iproperty. The value must be an ASCII string.$

-:32: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#32: FILE: drivers/gpu/drm/drm_connector.c:900:
+ * ^IFor DP MST connectors the path string follows the pattern$

-:33: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#33: FILE: drivers/gpu/drm/drm_connector.c:901:
+ * ^I"mst:<base connector ID>[-<mst port>]...", where the base connector ID$

-:34: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#34: FILE: drivers/gpu/drm/drm_connector.c:902:
+ * ^Iidentifies the DP connector on the source device, and the mst ports$

-:35: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#35: FILE: drivers/gpu/drm/drm_connector.c:903:
+ * ^Iare the port numbers in the DP MST topology.$

-:37: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#37: FILE: drivers/gpu/drm/drm_connector.c:905:
+ * ^IFor non-DP MST connectors the format is freeform, as long as it$

-:38: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#38: FILE: drivers/gpu/drm/drm_connector.c:906:
+ * ^Iuniquely identifies the physical path, remains stable across$

-:39: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#39: FILE: drivers/gpu/drm/drm_connector.c:907:
+ * ^Ikernel releases, and does not start with "mst:".$

total: 0 errors, 8 warnings, 0 checks, 25 lines checked
afe3bc73c941 drm/i915: Populate PATH prop for every connector

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

  parent reply	other threads:[~2019-06-13 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 18:43 [RFC][PATCH 0/2] drm: PATH prop for all connectors? Ville Syrjala
2019-06-13 18:43 ` [RFC][PATCH 1/2] drm: Improve PATH prop docs Ville Syrjala
2019-06-27  7:36   ` Pekka Paalanen
2019-06-13 18:43 ` [RFC][PATCH 2/2] drm/i915: Populate PATH prop for every connector Ville Syrjala
2019-06-27  7:37   ` Pekka Paalanen
2019-06-13 18:50 ` Patchwork [this message]
2019-06-13 20:42 ` [RFC][PATCH 0/2] drm: PATH prop for all connectors? Daniel Vetter
2019-06-27  7:35   ` Pekka Paalanen
2019-06-27  7:44     ` Michel Dänzer
2019-06-14 11:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-15  8:26 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-10 22:43 ` [Intel-gfx] [RFC][PATCH 0/2] " Lyude Paul
2019-07-11  7:20   ` Daniel Vetter
     [not found]   ` <20190711102923.3d219640@eldfell.localdomain>
2019-07-16 14:59     ` [Intel-gfx] " Li, Sun peng (Leo)
2019-08-01  9:51       ` Pekka Paalanen
2019-08-01 18:24         ` Li, Sun peng (Leo)

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=20190613185017.17470.75628@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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