From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Yi Liu" <yi.l.liu@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add vfio_device cdev for iommufd support
Date: Mon, 06 Feb 2023 11:55:40 -0000 [thread overview]
Message-ID: <167568454029.27496.1193171521353333674@emeril.freedesktop.org> (raw)
In-Reply-To: <20230206090532.95598-1-yi.l.liu@intel.com>
== Series Details ==
Series: Add vfio_device cdev for iommufd support
URL : https://patchwork.freedesktop.org/series/113696/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/113696/revisions/1/mbox/ not applied
Applying: vfio: Allocate per device file structure
Using index info to reconstruct a base tree...
M drivers/vfio/group.c
M drivers/vfio/vfio.h
M drivers/vfio/vfio_main.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/vfio/vfio_main.c
Auto-merging drivers/vfio/vfio.h
Auto-merging drivers/vfio/group.c
Applying: vfio: Refine vfio file kAPIs
error: sha1 information is lacking or useless (include/linux/vfio.h).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 vfio: Refine vfio file kAPIs
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".
prev parent reply other threads:[~2023-02-06 11:55 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 9:05 [PATCH v2 00/14] Add vfio_device cdev for iommufd support Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 01/14] vfio: Allocate per device file structure Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 02/14] vfio: Refine vfio file kAPIs Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-06 9:05 ` [PATCH v2 03/14] vfio: Accept vfio device file in the driver facing kAPI Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-07 3:25 ` Tian, Kevin
2023-02-07 3:25 ` [Intel-gfx] " Tian, Kevin
2023-02-06 9:05 ` [PATCH v2 04/14] kvm/vfio: Rename kvm_vfio_group to prepare for accepting vfio device fd Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-06 9:05 ` [PATCH v2 05/14] kvm/vfio: Accept vfio device file from userspace Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-07 3:36 ` Tian, Kevin
2023-02-07 3:36 ` [Intel-gfx] " Tian, Kevin
2023-02-07 8:39 ` Liu, Yi L
2023-02-07 8:39 ` [Intel-gfx] " Liu, Yi L
2023-02-06 9:05 ` [PATCH v2 06/14] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-07 3:42 ` Tian, Kevin
2023-02-07 3:42 ` [Intel-gfx] " Tian, Kevin
2023-02-06 9:05 ` [PATCH v2 07/14] vfio: Block device access via device fd until device is opened Yi Liu
2023-02-06 9:05 ` [Intel-gfx] " Yi Liu
2023-02-07 3:52 ` Tian, Kevin
2023-02-07 3:52 ` [Intel-gfx] " Tian, Kevin
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 08/14] vfio: Add infrastructure for bind_iommufd from userspace Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 3:56 ` [Intel-gfx] " Tian, Kevin
2023-02-07 3:56 ` Tian, Kevin
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 09/14] vfio-iommufd: Add detach_ioas support for physical VFIO devices Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 6:06 ` Tian, Kevin
2023-02-07 6:06 ` [Intel-gfx] " Tian, Kevin
2023-02-07 8:56 ` Liu, Yi L
2023-02-07 8:56 ` [Intel-gfx] " Liu, Yi L
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 10/14] vfio-iommufd: Add detach_ioas for emulated " Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 6:08 ` Tian, Kevin
2023-02-07 6:08 ` [Intel-gfx] " Tian, Kevin
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 11/14] vfio: Make vfio_device_open() exclusive between group path and device cdev path Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 6:24 ` Tian, Kevin
2023-02-07 6:24 ` [Intel-gfx] " Tian, Kevin
2023-02-07 8:54 ` Liu, Yi L
2023-02-07 8:54 ` [Intel-gfx] " Liu, Yi L
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 12/14] vfio: Add cdev for vfio_device Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 7:54 ` Tian, Kevin
2023-02-07 7:54 ` [Intel-gfx] " Tian, Kevin
2023-02-10 11:31 ` Joao Martins
2023-02-10 11:31 ` [Intel-gfx] " Joao Martins
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 13/14] vfio: Add ioctls for device cdev using iommufd Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-07 3:41 ` Yan Zhao
2023-02-07 3:41 ` [Intel-gfx] " Yan Zhao
2023-02-07 7:50 ` Liu, Yi L
2023-02-07 7:50 ` Liu, Yi L
2023-02-07 9:17 ` Tian, Kevin
2023-02-07 9:17 ` [Intel-gfx] " Tian, Kevin
2023-02-06 9:05 ` [Intel-gfx] [PATCH v2 14/14] vfio: Compile group optionally Yi Liu
2023-02-06 9:05 ` Yi Liu
2023-02-06 11:55 ` Patchwork [this message]
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=167568454029.27496.1193171521353333674@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yi.l.liu@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.