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 (rev14)
Date: Thu, 01 Aug 2019 18:17:33 -0000 [thread overview]
Message-ID: <20190801181733.30399.63706@emeril.freedesktop.org> (raw)
In-Reply-To: <20190801114119.28830-1-ramalingam.c@intel.com>
== Series Details ==
Series: HDCP2.2 Phase II (rev14)
URL : https://patchwork.freedesktop.org/series/57232/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ce79e1d0d5a1 drm: Add Content protection type property
-:146: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#146: FILE: drivers/gpu/drm/drm_hdcp.c:351:
+};
+DRM_ENUM_NAME_FN(drm_get_hdcp_content_type_name,
-:191: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#191: FILE: drivers/gpu/drm/drm_hdcp.c:404:
+ prop = drm_property_create_enum(dev, 0, "HDCP Content Type",
+ drm_hdcp_content_type_enum_list,
-:192: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#192: FILE: drivers/gpu/drm/drm_hdcp.c:405:
+ ARRAY_SIZE(
total: 0 errors, 0 warnings, 3 checks, 189 lines checked
5a8acad0bc86 drm/i915: Attach content type property
add126230c60 drm: uevent for connector status change
3b164c38b461 drm/hdcp: update content protection property with uevent
-:104: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#104: 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, 74 lines checked
f052ab943daa drm/i915: update the hdcp state with uevent
26394e4cc3b2 drm/hdcp: reference for srm file format
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-01 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 11:41 [PATCH v12 0/6] HDCP2.2 Phase II Ramalingam C
2019-08-01 11:41 ` [PATCH v12 1/6] drm: Add Content protection type property Ramalingam C
2019-08-01 11:41 ` [PATCH v12 2/6] drm/i915: Attach content " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 3/6] drm: uevent for connector status change Ramalingam C
2019-08-01 11:41 ` [PATCH v12 4/6] drm/hdcp: update content protection property with uevent Ramalingam C
2019-08-01 11:41 ` [PATCH v12 5/6] drm/i915: update the hdcp state " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 6/6] drm/hdcp: reference for srm file format Ramalingam C
2019-08-01 18:17 ` Patchwork [this message]
2019-08-01 18:43 ` ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev14) Patchwork
2019-08-02 7:04 ` Ramalingam C
2019-08-14 12:17 ` Martin Peres
2019-08-05 8:09 ` [Intel-gfx] [PATCH v12 0/6] HDCP2.2 Phase II Jani Nikula
2019-08-06 10:29 ` Ramalingam C
2019-08-14 14:30 ` ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev15) 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=20190801181733.30399.63706@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.