From: Anshuman Gupta <anshuman.gupta@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 0/2] HDCP 2.2 Comp fixes
Date: Thu, 20 Feb 2020 18:02:15 +0530 [thread overview]
Message-ID: <20200220123217.23635-1-anshuman.gupta@intel.com> (raw)
Adding ram's RB on patch1 and a new patch to fix DP HDCP Auth.
Anshuman Gupta (2):
drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg
drm/i915/hdcp: Return 0 on config_stream_type() +ve return
drivers/gpu/drm/i915/display/intel_hdcp.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-02-20 12:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 12:32 Anshuman Gupta [this message]
2020-02-20 12:32 ` [Intel-gfx] [PATCH v3 1/2] drm/i915/hdcp: Mandate (seq_num_V==0) at first RecvId msg Anshuman Gupta
2020-02-20 12:32 ` [Intel-gfx] [PATCH v3 2/2] drm/i915/hdcp: Return 0 on config_stream_type() +ve return Anshuman Gupta
2020-03-02 14:08 ` Ramalingam C
2020-03-03 5:24 ` [Intel-gfx] [PATCH v4 2/2] drm/i915/hdcp: Fix config_stream_type() ret value Anshuman Gupta
2020-03-03 5:43 ` Ramalingam C
2020-03-03 5:52 ` Anshuman Gupta
2020-03-03 6:25 ` Ramalingam C
2020-03-03 7:38 ` Anshuman Gupta
2020-03-03 10:20 ` Ramalingam C
2020-03-03 12:45 ` Anshuman Gupta
2020-02-20 20:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for HDCP 2.2 Comp fixes Patchwork
2020-02-23 5:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-03-03 6:05 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for HDCP 2.2 Comp fixes (rev2) Patchwork
2020-03-03 6:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-03 8:15 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for HDCP 2.2 Comp fixes (rev3) Patchwork
2020-03-03 8:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-03 16:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-03-04 1:43 ` [Intel-gfx] [PATCH v3 0/2] HDCP 2.2 Comp fixes Ramalingam C
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=20200220123217.23635-1-anshuman.gupta@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.