Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev2)
Date: Fri, 08 Mar 2019 17:25:30 -0000	[thread overview]
Message-ID: <20190308172530.11538.51419@emeril.freedesktop.org> (raw)
In-Reply-To: <20190308170008.10450-1-ramalingam.c@intel.com>

== Series Details ==

Series: HDCP2.2 Phase II (rev2)
URL   : https://patchwork.freedesktop.org/series/57232/
State : failure

== Summary ==

Series 57232 revision 2 Test-with: 20190308163049.9016-2-ramalingam.c@intel.com not found

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2019-03-08 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 17:00 [PATCH v2 0/8] HDCP2.2 Phase II Ramalingam C
2019-03-08 17:00 ` [PATCH v2 1/8] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-03-08 17:00 ` [PATCH v2 2/8] drm: Add Content protection type property Ramalingam C
2019-03-08 17:00 ` [PATCH v2 3/8] drm/i915: Attach content " Ramalingam C
2019-03-08 17:00 ` [PATCH v2 4/8] drm/i915: HDCP SRM parsing and revocation check Ramalingam C
2019-03-08 17:00 ` [PATCH v2 5/8] drm/i915/sysfs: Node for hdcp srm Ramalingam C
2019-03-08 17:00 ` [PATCH v2 6/8] drm: Add CP downstream_info property Ramalingam C
2019-03-08 17:00 ` [PATCH v2 7/8] drm/i915: Populate downstream info for HDCP1.4 Ramalingam C
2019-03-08 17:00 ` [PATCH v2 8/8] drm/i915: Populate downstream info for HDCP2.2 Ramalingam C
2019-03-08 17:25 ` Patchwork [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=20190308172530.11538.51419@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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