Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ashutosh Dixit" <ashutosh.dixit@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.Patch_applied: failure for Xe OA Consolidated Diffs
Date: Wed, 12 Jun 2024 01:58:33 -0000	[thread overview]
Message-ID: <171815751304.67160.276729366116015789@a6498e030952> (raw)
In-Reply-To: <20240612015303.2658884-1-ashutosh.dixit@intel.com>

== Series Details ==

Series: Xe OA Consolidated Diffs
URL   : https://patchwork.freedesktop.org/series/134742/
State : failure

== Summary ==

=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: 1340288da1f2 drm-tip: 2024y-06m-11d-21h-24m-08s UTC integration manifest
=== git am output follows ===
error: patch failed: drivers/gpu/drm/xe/instructions/xe_mi_commands.h:45
error: drivers/gpu/drm/xe/instructions/xe_mi_commands.h: patch does not apply
error: drivers/gpu/drm/xe/regs/xe_oa_regs.h: does not exist in index
error: patch failed: drivers/gpu/drm/xe/xe_device.c:41
error: drivers/gpu/drm/xe/xe_device.c: patch does not apply
error: patch failed: drivers/gpu/drm/xe/xe_guc_pc.c:193
error: drivers/gpu/drm/xe/xe_guc_pc.c: patch does not apply
error: patch failed: drivers/gpu/drm/xe/xe_guc_pc.h:9
error: drivers/gpu/drm/xe/xe_guc_pc.h: patch does not apply
error: patch failed: drivers/gpu/drm/xe/xe_module.c:10
error: drivers/gpu/drm/xe/xe_module.c: patch does not apply
error: drivers/gpu/drm/xe/xe_oa.c: does not exist in index
error: drivers/gpu/drm/xe/xe_oa.h: does not exist in index
error: drivers/gpu/drm/xe/xe_oa_types.h: does not exist in index
error: drivers/gpu/drm/xe/xe_perf.c: does not exist in index
error: drivers/gpu/drm/xe/xe_perf.h: does not exist in index
error: patch failed: include/uapi/drm/xe_drm.h:1374
error: include/uapi/drm/xe_drm.h: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Applying: drm/xe/oa: Combined diff of changes between v16 and v17
Patch failed at 0001 drm/xe/oa: Combined diff of changes between v16 and v17
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".



  parent reply	other threads:[~2024-06-12  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  1:53 [PATCH 0/1] Xe OA Consolidated Diffs Ashutosh Dixit
2024-06-12  1:53 ` [PATCH 1/1] drm/xe/oa: Combined diff of changes between v16 and v17 Ashutosh Dixit
2024-06-12  1:58 ` Patchwork [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-07 20:36 [PATCH 0/1] Xe OA Consolidated Diffs Ashutosh Dixit
2024-06-07 21:33 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-05-27  1:36 [PATCH 0/1] " Ashutosh Dixit
2024-05-27  1:41 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-05-24 18:24 [PATCH 0/1] " Ashutosh Dixit
2024-05-24 18:29 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-03-05  5:21 [PATCH 0/1] " Ashutosh Dixit
2024-03-05  5:26 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-01-20  1:49 [PATCH 0/1] " Ashutosh Dixit
2024-01-20  1:53 ` ✗ CI.Patch_applied: failure for " Patchwork

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=171815751304.67160.276729366116015789@a6498e030952 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=ashutosh.dixit@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