All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BUILD: failure for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all(). (rev2)
Date: Wed, 03 Apr 2024 09:51:21 -0000	[thread overview]
Message-ID: <171213788137.1155664.11661345599961343724@8e613ede5ea5> (raw)
In-Reply-To: <20240202154423.834991-1-maarten.lankhorst@linux.intel.com>

== Series Details ==

Series: series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all(). (rev2)
URL   : https://patchwork.freedesktop.org/series/129478/
State : failure

== Summary ==

Error: patch https://patchwork.freedesktop.org/api/1.0/series/129478/revisions/2/mbox/ not applied
Applying: drm: Add drm_vblank_work_flush_all().
Applying: drm/i915: Use vblank worker to unpin old legacy cursor fb safely
Using index info to reconstruct a base tree...
M	drivers/gpu/drm/i915/display/intel_cursor.c
M	drivers/gpu/drm/i915/display/intel_display.c
M	drivers/gpu/drm/i915/display/intel_display_types.h
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/display/intel_display_types.h
Auto-merging drivers/gpu/drm/i915/display/intel_display.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_display.c
Auto-merging drivers/gpu/drm/i915/display/intel_cursor.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 drm/i915: Use vblank worker to unpin old legacy cursor fb safely
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".
Build failed, no error log produced



  parent reply	other threads:[~2024-04-03  9:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 15:44 [CI 1/3] drm: Add drm_vblank_work_flush_all() Maarten Lankhorst
2024-02-02 15:44 ` [CI 2/3] drm/i915: Use vblank worker to unpin old legacy cursor fb safely Maarten Lankhorst
2024-02-02 15:44 ` [CI 3/3] drm/i915: Use the same vblank worker for atomic unpin Maarten Lankhorst
2024-02-02 16:28 ` ✓ CI.Patch_applied: success for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all() Patchwork
2024-02-02 16:28 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-02 16:29 ` ✓ CI.KUnit: success " Patchwork
2024-02-02 16:36 ` ✓ CI.Build: " Patchwork
2024-02-02 16:37 ` ✓ CI.Hooks: " Patchwork
2024-02-02 16:38 ` ✗ CI.checksparse: warning " Patchwork
2024-02-02 17:01 ` ✓ CI.BAT: success " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-02 19:42 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-02 21:10 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-03  9:51 ` Patchwork [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31 12:10 [CI 1/3] " Maarten Lankhorst
2024-02-02  4:53 ` ✗ Fi.CI.BUILD: failure for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all(). (rev2) 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=171213788137.1155664.11661345599961343724@8e613ede5ea5 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.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 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.