From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Nathan Chancellor" <nathan@kernel.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Fix CFI violations in gt_sysfs (rev2)
Date: Mon, 03 Oct 2022 22:58:05 -0000 [thread overview]
Message-ID: <166483788506.6048.4587689882551004459@emeril.freedesktop.org> (raw)
In-Reply-To: <20220922195127.2607496-1-nathan@kernel.org>
== Series Details ==
Series: drm/i915: Fix CFI violations in gt_sysfs (rev2)
URL : https://patchwork.freedesktop.org/series/108917/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/108917/revisions/2/mbox/ not applied
Applying: drm/i915: Fix CFI violations in gt_sysfs
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 drm/i915: Fix CFI violations in gt_sysfs
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".
prev parent reply other threads:[~2022-10-03 22:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:51 [PATCH] drm/i915: Fix CFI violations in gt_sysfs Nathan Chancellor
2022-09-22 19:51 ` [Intel-gfx] " Nathan Chancellor
2022-09-22 19:51 ` Nathan Chancellor
2022-09-22 23:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-09-23 0:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-23 6:58 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-23 7:15 ` [PATCH] " Tvrtko Ursulin
2022-09-23 7:15 ` [Intel-gfx] " Tvrtko Ursulin
2022-09-23 7:15 ` Tvrtko Ursulin
2022-09-24 4:57 ` Kees Cook
2022-09-24 4:57 ` [Intel-gfx] " Kees Cook
2022-09-24 4:57 ` Kees Cook
2022-09-25 4:39 ` Nathan Chancellor
2022-09-25 4:39 ` [Intel-gfx] " Nathan Chancellor
2022-09-25 4:39 ` Nathan Chancellor
2022-09-29 16:46 ` [Intel-gfx] " Andi Shyti
2022-09-29 16:46 ` Andi Shyti
2022-09-29 16:46 ` Andi Shyti
2022-09-29 16:53 ` Nathan Chancellor
2022-09-29 16:53 ` Nathan Chancellor
2022-09-29 16:53 ` Nathan Chancellor
2022-09-29 22:34 ` Andrzej Hajda
2022-09-29 22:44 ` Nathan Chancellor
2022-09-29 22:44 ` Nathan Chancellor
2022-09-29 22:44 ` Nathan Chancellor
2022-10-03 17:46 ` Nathan Chancellor
2022-10-03 17:46 ` Nathan Chancellor
2022-10-03 17:46 ` Nathan Chancellor
2022-10-03 22:58 ` 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=166483788506.6048.4587689882551004459@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nathan@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.