From: "Saarinen, Jani" <jani.saarinen@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
"Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-intel tree
Date: Tue, 8 May 2018 06:11:32 +0000 [thread overview]
Message-ID: <43D4F724E12AB6478FC1572B3FBE89D07606F0BB@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <20180508114052.69d7487f@canb.auug.org.au>
HI,
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
> Stephen Rothwell
> Sent: tiistai 8. toukokuuta 2018 4.41
> To: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for linux-next: build failure after
> merge of the drm-intel tree
>
> Hi all,
>
> On Tue, 08 May 2018 01:36:25 -0000 Patchwork
> <patchwork@emeril.freedesktop.org> wrote:
> >
> > == Series Details ==
> >
> > Series: linux-next: build failure after merge of the drm-intel tree
> > URL : https://patchwork.freedesktop.org/series/42839/
> > State : failure
>
> Blah, blah :-)
>
> Can someone please arrange for my linux-next merge fix patches to not be fed
> into your patchwork/ci as they will never work out side linux-next ...
Tomi, Arek? What can be done if any?
>
> --
> Cheers,
> Stephen Rothwell
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-08 6:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 1:07 linux-next: build failure after merge of the drm-intel tree Stephen Rothwell
2018-05-08 1:19 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-05-08 1:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-05-08 1:40 ` Stephen Rothwell
2018-05-08 6:11 ` Saarinen, Jani [this message]
2018-05-08 12:28 ` Arkadiusz Hiler
2018-05-08 7:08 ` Oleksandr Andrushchenko
2018-05-08 7:08 ` Oleksandr Andrushchenko
2018-05-09 5:02 ` Stephen Rothwell
2018-05-09 5:02 ` Stephen Rothwell
2018-05-09 5:08 ` Christoph Hellwig
2018-05-09 5:18 ` Stephen Rothwell
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=43D4F724E12AB6478FC1572B3FBE89D07606F0BB@IRSMSX106.ger.corp.intel.com \
--to=jani.saarinen@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomi.p.sarvela@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.