public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev4)
Date: Fri, 22 Mar 2019 03:26:01 -0000	[thread overview]
Message-ID: <20190322032601.14935.17822@emeril.freedesktop.org> (raw)
In-Reply-To: <20190322004448.14045-1-ramalingam.c@intel.com>

== Series Details ==

Series: HDCP2.2 Phase II (rev4)
URL   : https://patchwork.freedesktop.org/series/57232/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
e5c335d05858 drm/i915: debugfs: HDCP2.2 capability read
42027b987c97 drm: Add Content protection type property
-:60: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#60: FILE: drivers/gpu/drm/drm_connector.c:864:
+};
+DRM_ENUM_NAME_FN(drm_get_hdcp_content_type_name,

-:120: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#120: FILE: drivers/gpu/drm/drm_connector.c:1604:
+					ARRAY_SIZE(

-:178: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#178: FILE: include/drm/drm_connector.h:1325:
+int drm_connector_attach_hdcp_content_type_property(

total: 0 errors, 0 warnings, 3 checks, 146 lines checked
7d684b5665b1 drm/i915: Attach content type property
-:90: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#90: FILE: drivers/gpu/drm/i915/intel_hdcp.c:1785:
+	ret = drm_connector_attach_hdcp_content_type_property(

total: 0 errors, 0 warnings, 1 checks, 117 lines checked
feea572296ef drm/i915: HDCP SRM parsing and revocation check
2c2554ecdb1d drm/i915/sysfs: Node for hdcp srm
-:31: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IWUSR' are not preferred. Consider using octal permissions '0200'.
#31: FILE: drivers/gpu/drm/i915/i915_sysfs.c:591:
+	.attr = {.name = "hdcp_srm", .mode = S_IWUSR},

total: 0 errors, 1 warnings, 0 checks, 50 lines checked
1afee773fc6b drm: Add CP downstream_info property
-:130: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#130: FILE: drivers/gpu/drm/drm_connector.c:1686:
+drm_connector_update_hdcp_topology_property(struct drm_connector *connector,
+					const struct hdcp_topology_info *info)

-:139: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#139: FILE: drivers/gpu/drm/drm_connector.c:1695:
+	ret = drm_property_replace_global_blob(dev,
+			&connector->hdcp_topology_blob_ptr,

-:172: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#172: FILE: include/drm/drm_connector.h:1334:
+int drm_connector_attach_hdcp_topology_property(

-:174: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#174: FILE: include/drm/drm_connector.h:1336:
+int drm_connector_update_hdcp_topology_property(

total: 0 errors, 0 warnings, 4 checks, 171 lines checked
8e5349523c11 drm/i915: Populate downstream info for HDCP1.4
-:86: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#86: FILE: drivers/gpu/drm/i915/intel_hdcp.c:814:
+	if (drm_connector_update_hdcp_topology_property(&connector->base,
+						connector->hdcp.topology_info))

-:96: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#96: FILE: drivers/gpu/drm/i915/intel_hdcp.c:850:
+			if (drm_connector_update_hdcp_topology_property(

total: 0 errors, 0 warnings, 2 checks, 102 lines checked
df1b5d54c4ff drm/i915: Populate downstream info for HDCP2.2
-:56: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#56: FILE: drivers/gpu/drm/i915/intel_hdcp.c:1676:
+		drm_connector_update_hdcp_topology_property(&connector->base,
+							  hdcp->topology_info);

total: 0 errors, 0 warnings, 1 checks, 72 lines checked
780f3826157b drm: uevent for connector status change
c3cbb7db2b41 drm/i915: uevent for HDCP status change

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

  parent reply	other threads:[~2019-03-22  3:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  0:44 [PATCH v3 00/10] HDCP2.2 Phase II Ramalingam C
2019-03-22  0:44 ` [PATCH v3 01/10] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-03-27  9:51   ` Daniel Vetter
2019-03-22  0:44 ` [PATCH v3 02/10] drm: Add Content protection type property Ramalingam C
2019-03-27  9:56   ` Daniel Vetter
2019-03-27 13:34     ` Ramalingam C
2019-03-22  0:44 ` [PATCH v3 03/10] drm/i915: Attach content " Ramalingam C
2019-03-27 10:00   ` Daniel Vetter
2019-03-27 13:39     ` Ramalingam C
2019-03-22  0:44 ` [PATCH v3 04/10] drm/i915: HDCP SRM parsing and revocation check Ramalingam C
2019-03-27 10:16   ` Daniel Vetter
2019-03-27 13:48     ` Ramalingam C
2019-03-22  0:44 ` [PATCH v3 05/10] drm/i915/sysfs: Node for hdcp srm Ramalingam C
2019-03-22  0:44 ` [PATCH v3 06/10] drm: Add CP downstream_info property Ramalingam C
2019-03-27 10:25   ` Daniel Vetter
2019-03-27 14:00     ` Ramalingam C
2019-03-27 14:22       ` Daniel Vetter
2019-03-22  0:44 ` [PATCH v3 07/10] drm/i915: Populate downstream info for HDCP1.4 Ramalingam C
2019-03-27 10:28   ` Daniel Vetter
2019-03-22  0:44 ` [PATCH v3 08/10] drm/i915: Populate downstream info for HDCP2.2 Ramalingam C
2019-03-27 10:31   ` Daniel Vetter
2019-03-27 14:49     ` Ramalingam C
2019-03-27 17:44       ` Daniel Vetter
2019-03-22  0:44 ` [PATCH v3 09/10] drm: uevent for connector status change Ramalingam C
2019-03-27 11:00   ` Daniel Vetter
2019-03-27 11:01   ` Daniel Vetter
2019-03-27 14:40     ` Ramalingam C
2019-03-22  0:44 ` [PATCH v3 10/10] drm/i915: uevent for HDCP " Ramalingam C
2019-03-27 11:06   ` Daniel Vetter
2019-03-27 14:37     ` Ramalingam C
2019-03-27 17:47       ` Daniel Vetter
2019-03-22  3:26 ` Patchwork [this message]
2019-03-22  3:33 ` ✗ Fi.CI.SPARSE: warning for HDCP2.2 Phase II (rev4) Patchwork
2019-03-22  3:54 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-22 23:31 ` ✓ 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=20190322032601.14935.17822@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ramalingam.c@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