From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev5)
Date: Wed, 22 Nov 2023 19:12:40 +0000 [thread overview]
Message-ID: <8e855eb3de2dda79c96b5eececf80f822f272906.camel@intel.com> (raw)
In-Reply-To: <169581291678.20757.13627914580777505297@emeril.freedesktop.org>
On Wed, 2023-09-27 at 11:08 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev5)
> URL: https://patchwork.freedesktop.org/series/123803/
alan:snip
>
> Here are the unknown changes that may have been introduced in Patchwork_123803v5_full:
>
> IGT changes
> Possible regressions
>
> * igt@perf_pmu@frequency@gt0:
> * shard-dg2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13682/shard-dg2-11/igt@perf_pmu@frequency@gt0.html> -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_123803v5/shard-dg2-6/igt@perf_pmu@frequency@gt0.html>
alan: failure is verified as not related. but will post a rebase since its been a while.
next prev parent reply other threads:[~2023-11-22 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 18:04 [Intel-gfx] [PATCH v4] drm/i915/pxp: Add drm_dbgs for critical PXP events Alan Previn
2023-09-19 20:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev4) Patchwork
2023-09-26 23:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev5) Patchwork
2023-09-27 11:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-22 19:12 ` Teres Alexis, Alan Previn [this message]
2023-10-13 0:11 ` [Intel-gfx] [PATCH v4] drm/i915/pxp: Add drm_dbgs for critical PXP events Balasubrawmanian, Vivaik
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=8e855eb3de2dda79c96b5eececf80f822f272906.camel@intel.com \
--to=alan.previn.teres.alexis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox