From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for HDCP 2.2 and HDCP 1.4 Gen12 DP MST support (rev9)
Date: Wed, 13 Jan 2021 03:40:37 +0000 [thread overview]
Message-ID: <82d15f54af2a498daf676d40385ba192@intel.com> (raw)
In-Reply-To: <161035423345.25135.5682517583317741771@emeril.freedesktop.org>
Sparse warning was not related to this patch series.
Pushed to drm-intel-next.
Thanks for Reviews and Ack.
Thanks,
Anshuman Gupta
> -----Original Message-----
> From: Patchwork <patchwork@emeril.freedesktop.org>
> Sent: Monday, January 11, 2021 2:07 PM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: ✗ Fi.CI.SPARSE: warning for HDCP 2.2 and HDCP 1.4 Gen12 DP MST
> support (rev9)
>
> == Series Details ==
>
> Series: HDCP 2.2 and HDCP 1.4 Gen12 DP MST support (rev9)
> URL : https://patchwork.freedesktop.org/series/82998/
> State : warning
>
> == Summary ==
>
> $ dim sparse --fast origin/drm-tip
> Sparse version: v0.6.2
> Fast mode used, each commit won't be checked separately.
> -
> +./drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgv_sriovmsg.h:257:49:
> error: static assertion failed: "amd_sriov_msg_vf2pf_info must be 1 KB"
> +./drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgv_sriovmsg.h:261:49:
> error: static assertion failed: "amd_sriov_msg_pf2vf_info must be 1 KB"
> +drivers/gpu/drm/i915/gt/intel_reset.c:1329:5: warning: context
> imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block
> +drivers/gpu/drm/i915/gvt/mmio.c:295:23: warning: memcpy with byte
> count of 279040
> +drivers/gpu/drm/i915/i915_perf.c:1450:15: warning: memset with byte
> count of 16777216
> +drivers/gpu/drm/i915/i915_perf.c:1504:15: warning: memset with byte
> count of 16777216
> +./include/linux/seqlock.h:843:24: warning: trying to copy expression type
> 31
> +./include/linux/seqlock.h:843:24: warning: trying to copy expression type
> 31
> +./include/linux/seqlock.h:869:16: warning: trying to copy expression type
> 31
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_read16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_read32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_read64' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_read8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_write16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_write32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'fwtable_write8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_read16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_read32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_read64' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_read8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_write16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_write32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen11_fwtable_write8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_read16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_read32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_read64' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_read8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_write16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_write32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen12_fwtable_write8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_read16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_read32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_read64' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_read8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_write16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_write32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen6_write8' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen8_write16' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen8_write32' - different lock contexts for basic block
> +./include/linux/spinlock.h:409:9: warning: context imbalance in
> 'gen8_write8' - different lock contexts for basic block
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2021-01-13 3:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 8:11 [Intel-gfx] [PATCH v9 00/19] HDCP 2.2 and HDCP 1.4 Gen12 DP MST support Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 01/19] drm/i915/hdcp: Update CP property in update_pipe Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 02/19] drm/i915/hdcp: Get conn while content_type changed Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 03/19] drm/i915/hotplug: Handle CP_IRQ for DP-MST Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 04/19] drm/i915/hdcp: No HDCP when encoder is't initialized Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 05/19] drm/i915/hdcp: DP MST transcoder for link and stream Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 06/19] drm/i915/hdcp: Move HDCP enc status timeout to header Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 07/19] drm/i915/hdcp: HDCP stream encryption support Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 08/19] drm/i915/hdcp: Configure HDCP1.4 MST steram encryption status Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 09/19] drm/i915/hdcp: Enable Gen12 HDCP 1.4 DP MST support Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 10/19] drm/i915/hdcp: Pass dig_port to intel_hdcp_init Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 11/19] drm/i915/hdcp: Encapsulate hdcp_port_data to dig_port Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 12/19] misc/mei/hdcp: Fix AUTH_STREAM_REQ cmd buffer len Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 13/19] drm/hdcp: Max MST content streams Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 14/19] drm/i915/hdcp: MST streams support in hdcp port_data Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-12 5:26 ` [Intel-gfx] " Li, Juston
2021-01-12 5:26 ` Li, Juston
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 15/19] drm/i915/hdcp: Pass connector to check_2_2_link Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 16/19] drm/i915/hdcp: Add HDCP 2.2 stream register Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 17/19] drm/i915/hdcp: Support for HDCP 2.2 MST shim callbacks Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 18/19] drm/i915/hdcp: Configure HDCP2.2 MST steram encryption status Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:11 ` [Intel-gfx] [PATCH v9 19/19] drm/i915/hdcp: Enable HDCP 2.2 MST support Anshuman Gupta
2021-01-11 8:11 ` Anshuman Gupta
2021-01-11 8:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for HDCP 2.2 and HDCP 1.4 Gen12 DP MST support (rev9) Patchwork
2021-01-13 3:40 ` Gupta, Anshuman [this message]
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=82d15f54af2a498daf676d40385ba192@intel.com \
--to=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.