From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Sean Paul <sean@poorly.run>
To: Sean Paul <seanpaul@chromium.org>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: juston.li@intel.com, ramalingam.c@intel.com
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Ramalingam C <ramalingam.c@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v7 02/17] drm/i915: Clear the repeater bit on HDCP disable
Date: Thu, 25 Jun 2020 14:53:56 +0000 [thread overview]
Message-ID: <20200625145357.49F55207BB@mail.kernel.org> (raw)
In-Reply-To: <20200623155907.22961-3-sean@poorly.run>
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:
692059318c0fc ("drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+")
v4.19.129: Failed to apply! Possible dependencies:
0e39037b31655 ("drm/i915: Cache the error string")
16e4dd0342a80 ("drm/i915: Markup paired operations on wakerefs")
39e2f501c1b43 ("drm/i915: Split struct intel_context definition to its own header")
408bd91786665 ("drm/i915: extract intel_hdcp.h from intel_drv.h")
52c0fdb25c7c9 ("drm/i915: Replace global breadcrumbs with per-context interrupt tracking")
538ef96b9dae7 ("drm/i915/gem: Track the rpm wakerefs")
692059318c0fc ("drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+")
6b048706f407f ("drm/i915: Forcibly flush unwanted requests in drop-caches")
87f1ef225242d ("drm/i915: Record the sseu configuration per-context & engine")
95fd94a645f75 ("drm/i915: avoid rebuilding i915_gpu_error.o on version string updates")
c0a6aa7ec2c36 ("drm/i915: Show actual alongside requested frequency in debugfs/i915_rps_boost_info")
c2400ec3b6d15 ("drm/i915: add Makefile magic for testing headers are self-contained")
c44301fce6146 ("drm/i915: Allow control of PSR at runtime through debugfs, v6")
e0516e83640e1 ("drm/i915: Move sandybride pcode access to intel_sideband.c")
e1ef734eaec54 ("drm/i915: make intel_frontbuffer.h self-contained")
e6154e4cb8b0d ("drm/i915: Skip the ERR_PTR error state")
eb8d0f5af4ec2 ("drm/i915: Remove GPU reset dependence on struct_mutex")
fb6f0b64e455b ("drm/i915: Prevent machine hang from Broxton's vtd w/a and error capture")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-06-25 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200623155907.22961-1-sean@poorly.run>
2020-06-23 15:58 ` [PATCH v7 01/17] drm/i915: Fix sha_text population code Sean Paul
2020-06-25 14:53 ` Sasha Levin
2020-06-23 15:58 ` [PATCH v7 02/17] drm/i915: Clear the repeater bit on HDCP disable Sean Paul
2020-06-25 14:53 ` Sasha Levin [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=20200625145357.49F55207BB@mail.kernel.org \
--to=sashal@kernel.org \
--cc=juston.li@intel.com \
--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).