[Intel-gfx] [PATCH v7 01/17] drm/i915: Fix sha_text population code
Sasha Levin
sashal at kernel.org
Thu Jun 25 14:53:59 UTC 2020
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: ee5e5e7a5e0f ("drm/i915: Add HDCP framework + base implementation").
The bot has tested the following trees: v5.7.5, v5.4.48, v4.19.129.
v5.7.5: Build OK!
v5.4.48: Failed to apply! Possible dependencies:
65833c463886f ("drm/i915/hdcp: conversion to struct drm_device based logging macros.")
667944ad77f19 ("drm/i915/hdcp: use intel_de_*() functions for register access")
692059318c0fc ("drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+")
v4.19.129: Failed to apply! Possible dependencies:
04707f9716363 ("drm/i915: Initialize HDCP2.2")
09d56393c1d8d ("drm/i915: hdcp1.4 CP_IRQ handling and SW encryption tracking")
2f80d7bd8d93c ("drm/i915: drop all drmP.h includes")
33b7f3ee6e008 ("drm/i915: Add CRTC output format YCBCR 4:2:0")
340a44bef2342 ("drm/i915/icl: program MG_DP_MODE")
342ac601df642 ("drm/i915: hdcp_check_link only on CP_IRQ")
47658556da857 ("drm/i915/dp: Do not grab crtc modeset lock in intel_dp_detect()")
667944ad77f19 ("drm/i915/hdcp: use intel_de_*() functions for register access")
668b6c176c33f ("drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON")
7b610f1fbed2a ("drm/i915/dp: Add DSC params and DSC config to intel_crtc_state")
9055aac76589c ("drm/i915: MEI interface implementation")
9844bc87cb7a5 ("drm/i915/dp: Fix duplication of DEVICE_SERVICE_IRQ handling")
bdc93fe0eb82f ("drm/i915/debugfs: hdcp capability of a sink")
cbfa8ac835cb4 ("drm/i915/dp: Kill intel_dp->detect_done flag")
d3dacc70797b8 ("drm/i915: wrapping all hdcp var into intel_hdcp")
d5acd97f55711 ("drm/i915/dp: Use a local variable for intel_encoder *")
d78aa650670d2 ("drm: Add drm/drm_util.h header file")
de25eb7f3075f ("drm/i915: introduce dp_to_i915() helper")
f106d1005ac72 ("drm/i915: Pullout the bksv read and validation")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
More information about the Intel-gfx
mailing list