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: , intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sean Paul <seanpaul@chromium.org>,
stable@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v3 01/12] drm/i915: Fix sha_text population code
Date: Sun, 19 Jan 2020 15:26:49 +0000 [thread overview]
Message-ID: <20200119152651.417F720678@mail.kernel.org> (raw)
In-Reply-To: <20200117193103.156821-2-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.4.13, v4.19.97.
v5.4.13: Build OK!
v4.19.97: Failed to apply! Possible dependencies:
Unable to calculate
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
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: , intel-gfx@lists.freedesktop.org,
Sean Paul <seanpaul@chromium.org>,
stable@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH v3 01/12] drm/i915: Fix sha_text population code
Date: Sun, 19 Jan 2020 15:26:49 +0000 [thread overview]
Message-ID: <20200119152651.417F720678@mail.kernel.org> (raw)
In-Reply-To: <20200117193103.156821-2-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.4.13, v4.19.97.
v5.4.13: Build OK!
v4.19.97: Failed to apply! Possible dependencies:
Unable to calculate
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-19 15:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:30 [PATCH v3 00/12] drm/i915: Add support for HDCP 1.4 over MST connectors Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 01/12] drm/i915: Fix sha_text population code Sean Paul
2020-01-17 19:30 ` Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-19 15:26 ` Sasha Levin [this message]
2020-01-19 15:26 ` Sasha Levin
2020-01-17 19:30 ` [PATCH v3 02/12] drm/i915: Clear the repeater bit on HDCP disable Sean Paul
2020-01-17 19:30 ` Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-19 15:26 ` Sasha Levin
2020-01-19 15:26 ` [Intel-gfx] " Sasha Levin
2020-01-17 19:30 ` [PATCH v3 03/12] drm/i915: WARN if HDCP signalling is enabled upon disable Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 04/12] drm/i915: Intercept Aksv writes in the aux hooks Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 05/12] drm/i915: Use the cpu_transcoder in intel_hdcp to toggle HDCP signalling Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 06/12] drm/i915: Factor out hdcp->value assignments Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 07/12] drm/i915: Protect workers against disappearing connectors Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-01-17 19:30 ` [PATCH v3 08/12] drm/i915: Don't fully disable HDCP on a port if multiple pipes are using it Sean Paul
2020-01-17 19:30 ` [Intel-gfx] " Sean Paul
2020-02-02 19:03 ` Ramalingam C
2020-02-02 19:03 ` [Intel-gfx] " Ramalingam C
2020-02-18 22:07 ` Sean Paul
2020-02-18 22:07 ` [Intel-gfx] " Sean Paul
2020-01-17 19:31 ` [PATCH v3 09/12] drm/i915: Support DP MST in enc_to_dig_port() function Sean Paul
2020-01-17 19:31 ` [Intel-gfx] " Sean Paul
2020-01-17 19:31 ` [PATCH v3 10/12] drm/i915: Use ddi_update_pipe in intel_dp_mst Sean Paul
2020-01-17 19:31 ` [Intel-gfx] " Sean Paul
2020-01-17 19:31 ` [PATCH v3 11/12] drm/i915: Factor out HDCP shim functions from dp for use by dp_mst Sean Paul
2020-01-17 19:31 ` [Intel-gfx] " Sean Paul
2020-01-17 19:31 ` [PATCH v3 12/12] drm/i915: Add HDCP 1.4 support for MST connectors Sean Paul
2020-01-17 19:31 ` [Intel-gfx] " Sean Paul
2020-01-18 2:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add support for HDCP 1.4 over MST connectors (rev3) Patchwork
2020-01-18 3:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-18 3:18 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-20 19:46 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2020-01-27 14:06 ` [PATCH v3 00/12] drm/i915: Add support for HDCP 1.4 over MST connectors Sean Paul
2020-01-27 14:06 ` [Intel-gfx] " Sean Paul
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=20200119152651.417F720678@mail.kernel.org \
--to=sashal@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.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.