All of lore.kernel.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 (rev11)
Date: Mon, 08 Jul 2019 18:26:49 -0000	[thread overview]
Message-ID: <20190708182649.21808.74301@emeril.freedesktop.org> (raw)
In-Reply-To: <20190708112116.1780-1-ramalingam.c@intel.com>

== Series Details ==

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

== Summary ==

$ dim checkpatch origin/drm-tip
4850c38d571b drm: Add Content protection type property
-:123: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#123: FILE: drivers/gpu/drm/drm_hdcp.c:351:
+};
+DRM_ENUM_NAME_FN(drm_get_hdcp_content_type_name,

-:168: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#168: FILE: drivers/gpu/drm/drm_hdcp.c:404:
+		prop = drm_property_create_enum(dev, 0, "HDCP Content Type",
+					drm_hdcp_content_type_enum_list,

-:169: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#169: FILE: drivers/gpu/drm/drm_hdcp.c:405:
+					ARRAY_SIZE(

total: 0 errors, 0 warnings, 3 checks, 182 lines checked
3bc2f2d69357 drm/i915: Attach content type property
80479a8101ac drm: uevent for connector status change
d37bd325f08f drm/hdcp: update content protection property with uevent
-:99: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#99: FILE: drivers/gpu/drm/drm_hdcp.c:448:
+	drm_sysfs_connector_status_event(connector,
+				 dev->mode_config.content_protection_property);

total: 0 errors, 0 warnings, 1 checks, 72 lines checked
ee2bd3463203 drm/i915: update the hdcp state with uevent
584ff79d12ea drm/hdcp: reference for srm file format

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

  parent reply	other threads:[~2019-07-08 18:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 11:21 [PATCH v9 0/6] HDCP2.2 Phase II Ramalingam C
2019-07-08 11:21 ` [PATCH v9 1/6] drm: Add Content protection type property Ramalingam C
2019-07-09 14:31   ` Pekka Paalanen
2019-07-09 12:47     ` Ramalingam C
2019-07-10  8:16       ` Pekka Paalanen
2019-07-11  5:50         ` Ramalingam C
2019-07-12 11:11           ` Pekka Paalanen
2019-07-12  4:43             ` Ramalingam C
2019-07-11 14:18   ` [Intel-gfx] " Sean Paul
2019-07-11 23:38     ` Ramalingam C
2019-07-12 11:39     ` Pekka Paalanen
2019-07-16 20:44       ` Sean Paul
2019-07-08 11:21 ` [PATCH v9 2/6] drm/i915: Attach content " Ramalingam C
2019-07-08 11:21 ` [PATCH v9 3/6] drm: uevent for connector status change Ramalingam C
2019-07-11 15:32   ` [Intel-gfx] " Sean Paul
2019-07-08 11:21 ` [PATCH v9 4/6] drm/hdcp: update content protection property with uevent Ramalingam C
2019-07-09 14:39   ` Pekka Paalanen
2019-07-08 11:21 ` [PATCH v9 5/6] drm/i915: update the hdcp state " Ramalingam C
2019-07-08 11:21 ` [PATCH v9 6/6] drm/hdcp: reference for srm file format Ramalingam C
2019-07-08 18:26 ` Patchwork [this message]
2019-07-08 18:43 ` ✓ Fi.CI.BAT: success for HDCP2.2 Phase II (rev11) Patchwork
2019-07-09  7:08 ` ✓ 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=20190708182649.21808.74301@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 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.