Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.Patch_applied: failure for Replace xe_hmm with gpusvm (rev4)
Date: Mon, 26 May 2025 21:59:15 -0000	[thread overview]
Message-ID: <174829675504.21444.6131527396166330311@1538d3639d33> (raw)
In-Reply-To: <20250512150637.61462-10-matthew.auld@intel.com>

== Series Details ==

Series: Replace xe_hmm with gpusvm (rev4)
URL   : https://patchwork.freedesktop.org/series/146553/
State : failure

== Summary ==

=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: 3e019cc3eaff drm-tip: 2025y-05m-26d-14h-49m-23s UTC integration manifest
=== git am output follows ===
error: patch failed: drivers/gpu/drm/drm_gpusvm.c:1362
error: drivers/gpu/drm/drm_gpusvm.c: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Applying: drm/gpusvm: fix hmm_pfn_to_map_order() usage
Applying: drm/gpusvm: use more selective dma dir in get_pages()
Patch failed at 0002 drm/gpusvm: use more selective dma dir in get_pages()
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:[~2025-05-26 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 15:06 [PATCH v4 0/8] Replace xe_hmm with gpusvm Matthew Auld
2025-05-12 15:06 ` [PATCH v4 1/8] drm/gpusvm: fix hmm_pfn_to_map_order() usage Matthew Auld
2025-05-12 15:06 ` [PATCH v4 2/8] drm/gpusvm: use more selective dma dir in get_pages() Matthew Auld
2025-05-12 15:06 ` [PATCH v4 3/8] drm/gpusvm: pull out drm_gpusvm_pages substructure Matthew Auld
2025-05-12 15:06 ` [PATCH v4 4/8] drm/gpusvm: refactor core API to use pages struct Matthew Auld
2025-05-12 15:06 ` [PATCH v4 5/8] drm/gpusvm: export drm_gpusvm_pages API Matthew Auld
2025-05-12 15:06 ` [PATCH v4 6/8] drm/xe/vm: split userptr bits into separate file Matthew Auld
2025-06-09 17:05   ` Matthew Brost
2025-05-12 15:06 ` [PATCH v4 7/8] drm/xe/userptr: replace xe_hmm with gpusvm Matthew Auld
2025-06-09 17:09   ` Matthew Brost
2025-05-12 15:06 ` [PATCH v4 8/8] drm/xe/pt: unify xe_pt_svm_pre_commit with userptr Matthew Auld
2025-05-12 16:27 ` ✓ CI.Patch_applied: success for Replace xe_hmm with gpusvm (rev4) Patchwork
2025-05-12 16:27 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-12 16:28 ` ✓ CI.KUnit: success " Patchwork
2025-05-12 16:38 ` ✗ CI.Build: failure " Patchwork
2025-05-13 11:04 ` ✗ CI.Patch_applied: " Patchwork
2025-05-26 21:59 ` 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=174829675504.21444.6131527396166330311@1538d3639d33 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@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