Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Vaishali Thakkar <vthakkar1994@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/core: Remove drm_dev_unref() and it's uses
Date: Thu, 26 Apr 2018 11:57:06 -0000	[thread overview]
Message-ID: <20180426115706.15161.54384@emeril.freedesktop.org> (raw)
In-Reply-To: <20180426102819.6985-1-vthakkar1994@gmail.com>

== Series Details ==

Series: drm/core: Remove drm_dev_unref() and it's uses
URL   : https://patchwork.freedesktop.org/series/42325/
State : failure

== Summary ==

Applying: drm/core: Remove drm_dev_unref() and it's uses
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	drivers/gpu/drm/drm_drv.c
M	drivers/gpu/drm/exynos/exynos_drm_drv.c
M	drivers/gpu/drm/mxsfb/mxsfb_drv.c
M	drivers/gpu/drm/omapdrm/omap_drv.c
M	drivers/gpu/drm/sti/sti_drv.c
M	drivers/gpu/drm/stm/drv.c
M	drivers/gpu/drm/tegra/drm.c
M	drivers/gpu/drm/tinydrm/core/tinydrm-core.c
M	drivers/gpu/drm/udl/udl_drv.c
M	drivers/gpu/drm/vc4/vc4_drv.c
M	include/drm/drm_drv.h
Falling back to patching base and 3-way merge...
Auto-merging include/drm/drm_drv.h
Auto-merging drivers/gpu/drm/vc4/vc4_drv.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/vc4/vc4_drv.c
Auto-merging drivers/gpu/drm/udl/udl_drv.c
Auto-merging drivers/gpu/drm/tinydrm/core/tinydrm-core.c
Auto-merging drivers/gpu/drm/tegra/drm.c
Auto-merging drivers/gpu/drm/stm/drv.c
Auto-merging drivers/gpu/drm/sti/sti_drv.c
Auto-merging drivers/gpu/drm/omapdrm/omap_drv.c
Auto-merging drivers/gpu/drm/mxsfb/mxsfb_drv.c
Auto-merging drivers/gpu/drm/exynos/exynos_drm_drv.c
Auto-merging drivers/gpu/drm/drm_drv.c
Patch failed at 0001 drm/core: Remove drm_dev_unref() and it's uses
The copy of the patch that failed is found in: .git/rebase-apply/patch
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".

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-04-26 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 10:28 [PATCH] drm/core: Remove drm_dev_unref() and it's uses Vaishali Thakkar
2018-04-26 10:43 ` Laurent Pinchart
2018-04-26 11:57 ` Patchwork [this message]
2018-04-26 12:06 ` Thierry Reding
2018-04-26 12:15 ` Boris Brezillon
     [not found] ` <20180426102819.6985-1-vthakkar1994-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-04-26 12:36   ` [Intel-gfx] " Daniel Vetter
     [not found]     ` <20180426123615.GA12521-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-04-26 12:45       ` Laurent Pinchart
2018-04-26 12:57         ` Vaishali Thakkar
2018-04-26 13:14         ` Alexandre Belloni
     [not found]           ` <20180426131404.GP4813-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2018-04-26 13:52             ` Daniel Vetter

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=20180426115706.15161.54384@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vthakkar1994@gmail.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