All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-misc tree
Date: Wed, 28 Aug 2019 15:27:50 -0000	[thread overview]
Message-ID: <20190828152750.28912.93076@emeril.freedesktop.org> (raw)
In-Reply-To: <20190828185516.22b03da8@canb.auug.org.au>

== Series Details ==

Series: linux-next: build failure after merge of the drm-misc tree
URL   : https://patchwork.freedesktop.org/series/65916/
State : failure

== Summary ==

Applying: linux-next: build failure after merge of the drm-misc tree
Using index info to reconstruct a base tree...
M	drivers/gpu/drm/virtio/virtgpu_object.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.

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

  parent reply	other threads:[~2019-08-28 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  8:55 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2019-08-28  8:55 ` Stephen Rothwell
2019-08-28  9:15 ` Gerd Hoffmann
2019-08-28 15:27 ` Patchwork [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-07  3:21 Stephen Rothwell
2019-08-07  3:48 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-14  4:41 Stephen Rothwell
2019-06-14  4:47 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-14  6:42   ` Stephen Rothwell
2019-06-18  8:11     ` Jani Nikula

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=20190828152750.28912.93076@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sfr@canb.auug.org.au \
    /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.