From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for HDCP2.2 Phase II (rev9)
Date: Tue, 07 May 2019 16:52:35 -0000 [thread overview]
Message-ID: <20190507165235.856.30830@emeril.freedesktop.org> (raw)
In-Reply-To: <20190507162745.25600-1-ramalingam.c@intel.com>
== Series Details ==
Series: HDCP2.2 Phase II (rev9)
URL : https://patchwork.freedesktop.org/series/57232/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm: move content protection property to mode_config
Okay!
Commit: drm/i915: debugfs: HDCP2.2 capability read
Okay!
Commit: drm: generic fn converting be24 to cpu and vice versa
Okay!
Commit: drm: revocation check at drm subsystem
+drivers/gpu/drm/drm_hdcp.c:235:6: warning: symbol 'drm_hdcp_request_srm' was not declared. Should it be static?
+drivers/gpu/drm/drm_hdcp.c:27:3: warning: symbol 'srm_data' was not declared. Should it be static?
+drivers/gpu/drm/drm_hdcp.c:317:5: warning: symbol 'drm_setup_hdcp_srm' was not declared. Should it be static?
+drivers/gpu/drm/drm_hdcp.c:327:6: warning: symbol 'drm_teardown_hdcp_srm' was not declared. Should it be static?
+./include/linux/slab.h:666:13: error: not a function <noident>
+./include/linux/slab.h:666:13: error: undefined identifier '__builtin_mul_overflow'
+./include/linux/slab.h:666:13: warning: call with no type!
Commit: drm/i915: SRM revocation check for HDCP1.4 and 2.2
Okay!
Commit: drm/hdcp: gathering hdcp related code into drm_hdcp.c
Okay!
Commit: drm: Add Content protection type property
Okay!
Commit: drm/i915: Attach content type property
Okay!
Commit: drm: uevent for connector status change
Okay!
Commit: drm/hdcp: update content protection property with uevent
Okay!
Commit: drm/i915: update the hdcp state with uevent
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-07 16:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:27 [PATCH v7 00/11] HDCP2.2 Phase II Ramalingam C
2019-05-07 16:27 ` [PATCH v7 01/11] drm: move content protection property to mode_config Ramalingam C
2019-05-07 16:27 ` [PATCH v7 02/11] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-05-07 16:27 ` [PATCH v7 03/11] drm: generic fn converting be24 to cpu and vice versa Ramalingam C
2019-05-07 16:27 ` [PATCH v7 04/11] drm: revocation check at drm subsystem Ramalingam C
2019-07-04 10:53 ` Pekka Paalanen
2019-09-12 0:15 ` Harry Wentland
2019-09-12 1:14 ` Deucher, Alexander
2019-09-12 6:54 ` Ramalingam C
2019-09-12 15:49 ` Harry Wentland
2019-05-07 16:27 ` [PATCH v7 05/11] drm/i915: SRM revocation check for HDCP1.4 and 2.2 Ramalingam C
2019-05-07 16:27 ` [PATCH v7 06/11] drm/hdcp: gathering hdcp related code into drm_hdcp.c Ramalingam C
2019-05-07 16:27 ` [PATCH v7 07/11] drm: Add Content protection type property Ramalingam C
2019-07-04 11:11 ` Pekka Paalanen
2019-07-04 10:36 ` Ramalingam C
2019-07-05 13:00 ` Pekka Paalanen
2019-07-05 6:33 ` Ramalingam C
2019-07-05 14:12 ` Pekka Paalanen
2019-05-07 16:27 ` [PATCH v7 08/11] drm/i915: Attach content " Ramalingam C
2019-05-07 16:27 ` [PATCH v7 09/11] drm: uevent for connector status change Ramalingam C
2019-05-10 12:12 ` Paul Kocialkowski
2019-05-10 14:54 ` Daniel Vetter
2019-05-13 9:02 ` Paul Kocialkowski
2019-05-13 9:34 ` Daniel Vetter
2019-05-13 10:11 ` Ser, Simon
2019-05-13 15:04 ` Daniel Vetter
2019-05-14 6:18 ` Ser, Simon
2019-05-13 17:14 ` Paul Kocialkowski
2019-05-14 11:09 ` Daniel Vetter
2019-05-14 14:12 ` Paul Kocialkowski
2019-05-14 14:28 ` Daniel Vetter
2019-05-15 7:43 ` Paul Kocialkowski
2019-05-15 7:48 ` Daniel Vetter
2019-05-14 8:02 ` Pekka Paalanen
2019-05-14 8:18 ` Ser, Simon
2019-05-14 11:02 ` Daniel Vetter
2019-05-14 13:36 ` Pekka Paalanen
2019-05-14 13:58 ` Paul Kocialkowski
2019-05-14 14:34 ` Daniel Vetter
2019-05-15 7:37 ` Pekka Paalanen
2019-05-15 7:49 ` Paul Kocialkowski
2019-05-15 8:24 ` Daniel Vetter
2019-05-16 8:22 ` Pekka Paalanen
2019-05-16 12:24 ` Daniel Vetter
2019-05-17 10:08 ` Pekka Paalanen
2019-05-20 16:11 ` Daniel Vetter
2019-05-20 16:24 ` Paul Kocialkowski
2019-05-21 6:55 ` Pekka Paalanen
2019-05-21 7:52 ` Daniel Vetter
2019-05-21 9:01 ` Pekka Paalanen
2019-05-21 9:42 ` Daniel Vetter
2019-06-03 9:50 ` Michel Dänzer
2019-06-03 15:08 ` Daniel Vetter
2019-06-03 15:19 ` Ser, Simon
2019-06-04 7:06 ` Pekka Paalanen
2019-05-13 21:20 ` Lyude Paul
2019-05-14 11:12 ` Daniel Vetter
2019-07-04 11:12 ` Pekka Paalanen
2019-07-04 10:42 ` Ramalingam C
2019-07-05 13:36 ` Pekka Paalanen
2019-05-07 16:27 ` [PATCH v7 10/11] drm/hdcp: update content protection property with uevent Ramalingam C
2019-07-04 11:14 ` Pekka Paalanen
2019-07-04 11:11 ` Ramalingam C
2019-07-05 13:59 ` Pekka Paalanen
2019-07-04 23:51 ` Ramalingam C
2019-05-07 16:27 ` [PATCH v7 11/11] drm/i915: update the hdcp state " Ramalingam C
2019-05-07 16:45 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev9) Patchwork
2019-05-07 16:52 ` Patchwork [this message]
2019-05-07 17:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-08 0:41 ` ✓ 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=20190507165235.856.30830@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;
as well as URLs for NNTP newsgroup(s).