Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.Patch_applied: failure for series starting with [i-g-t,1/5] tests/intel/xe_pm: Update runtime pm conditions
Date: Mon, 13 May 2024 16:03:22 -0400	[thread overview]
Message-ID: <ZkJyCsAqvaZRKAGA@intel.com> (raw)
In-Reply-To: <171562690261.2095830.4760834802357791232@8e613ede5ea5>

On Mon, May 13, 2024 at 07:01:42PM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: series starting with [i-g-t,1/5] tests/intel/xe_pm: Update runtime pm conditions
> URL   : https://patchwork.freedesktop.org/series/133566/
> State : failure
> 
> == Summary ==
> 
> === Applying kernel patches on branch 'drm-tip' with base: ===
> Base commit: 3d00e04692d4 drm-tip: 2024y-05m-13d-17h-13m-55s UTC integration manifest

CI should stop trying to apply patches with subject-prefix containing "PATCH i-g-t" on a kernel tree.

> === git am output follows ===
> error: lib/igt_pm.c: does not exist in index
> error: lib/igt_pm.h: does not exist in index
> error: tests/intel/xe_pm.c: does not exist in index
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> Applying: tests/intel/xe_pm: Update runtime pm conditions
> Patch failed at 0001 tests/intel/xe_pm: Update runtime pm conditions
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> 
> 

  reply	other threads:[~2024-05-13 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 18:55 [PATCH i-g-t 1/5] tests/intel/xe_pm: Update runtime pm conditions Rodrigo Vivi
2024-05-13 18:55 ` [PATCH i-g-t 2/5] lib/igt_pm: Fix and standardize IGT PM library documentation Rodrigo Vivi
2024-05-14  6:49   ` Riana Tauro
2024-05-13 18:55 ` [PATCH i-g-t 3/5] tests/intel/xe_pm: Also disable display for mmap_system test Rodrigo Vivi
2024-05-14  6:12   ` Gupta, Anshuman
2024-05-14  6:46   ` Nilawar, Badal
2024-05-13 18:55 ` [PATCH i-g-t 4/5] tests/intel/xe_pm: Only check the rpm resume after the first mmap operation Rodrigo Vivi
2024-05-14 15:19   ` Nilawar, Badal
2024-05-14 16:39     ` Nilawar, Badal
2024-05-13 18:55 ` [PATCH i-g-t 5/5] tests/intel/xe_pm: Convert mmap tests to use existing d3 helpers Rodrigo Vivi
2024-05-13 19:01 ` ✗ CI.Patch_applied: failure for series starting with [i-g-t,1/5] tests/intel/xe_pm: Update runtime pm conditions Patchwork
2024-05-13 20:03   ` Rodrigo Vivi [this message]
2024-05-16 16:49 ` [PATCH i-g-t 1/5] " Francois Dugast

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=ZkJyCsAqvaZRKAGA@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@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