From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for linux-next: build failure after merge of the drm-misc tree
Date: Thu, 17 Nov 2022 07:54:06 -0000 [thread overview]
Message-ID: <166867164674.12185.5741791351392944341@emeril.freedesktop.org> (raw)
In-Reply-To: <20221117183214.2473e745@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/111006/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/111006/revisions/1/mbox/ not applied
Patch is empty.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To record the empty patch as an empty commit, run "git am --allow-empty".
To restore the original branch and stop patching, run "git am --abort".
next prev parent reply other threads:[~2022-11-17 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 7:32 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2022-11-17 7:32 ` Stephen Rothwell
2022-11-17 7:32 ` [Intel-gfx] " Stephen Rothwell
2022-11-17 7:54 ` Patchwork [this message]
2022-11-23 5:20 ` Stephen Rothwell
2022-11-23 5:20 ` [Intel-gfx] " Stephen Rothwell
2022-11-23 5:20 ` Stephen Rothwell
2022-11-23 5:35 ` David Airlie
2022-11-23 5:35 ` David Airlie
2022-11-23 5:35 ` [Intel-gfx] " David Airlie
2022-11-23 6:22 ` Stephen Rothwell
2022-11-23 6:22 ` [Intel-gfx] " Stephen Rothwell
2022-11-23 6:22 ` Stephen Rothwell
2022-11-23 8:33 ` Thomas Zimmermann
2022-11-23 8:33 ` [Intel-gfx] " Thomas Zimmermann
2022-11-23 8:33 ` Thomas Zimmermann
-- strict thread matches above, loose matches on Subject: below --
2021-06-08 2:50 Stephen Rothwell
2021-06-08 3:28 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " 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=166867164674.12185.5741791351392944341@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.