From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>,
Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.a.wang@intel.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] vfio-mdev: remove an non-existing driver from vfio-mediated-device
Date: Tue, 10 Jan 2023 09:49:44 -0500 [thread overview]
Message-ID: <625de375-562d-3a72-830b-4c4835ab93e6@linux.ibm.com> (raw)
In-Reply-To: <20230110091009.474427-5-hch@lst.de>
LGTM
Reviewed-by: Tony Krowiak <akrowiak@linux.ibm.com>
On 1/10/23 4:10 AM, Christoph Hellwig wrote:
> The nvidia mdev driver does not actually exist anywhere in the tree.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> Documentation/driver-api/vfio-mediated-device.rst | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/Documentation/driver-api/vfio-mediated-device.rst b/Documentation/driver-api/vfio-mediated-device.rst
> index d4267243b4f525..bbd548b66b4255 100644
> --- a/Documentation/driver-api/vfio-mediated-device.rst
> +++ b/Documentation/driver-api/vfio-mediated-device.rst
> @@ -60,7 +60,7 @@ devices as examples, as these devices are the first devices to use this module::
> | mdev.ko |
> | +-----------+ | mdev_register_parent() +--------------+
> | | | +<------------------------+ |
> - | | | | | nvidia.ko |<-> physical
> + | | | | | ccw_device.ko|<-> physical
> | | | +------------------------>+ | device
> | | | | callbacks +--------------+
> | | Physical | |
> @@ -69,12 +69,6 @@ devices as examples, as these devices are the first devices to use this module::
> | | | | | i915.ko |<-> physical
> | | | +------------------------>+ | device
> | | | | callbacks +--------------+
> - | | | |
> - | | | | mdev_register_parent() +--------------+
> - | | | +<------------------------+ |
> - | | | | | ccw_device.ko|<-> physical
> - | | | +------------------------>+ | device
> - | | | | callbacks +--------------+
> | +-----------+ |
> +---------------+
>
next prev parent reply other threads:[~2023-01-10 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 9:10 misc mdev tidyups Christoph Hellwig
2023-01-10 9:10 ` [PATCH 1/4] vfio-mdev: allow building the samples into the kernel Christoph Hellwig
2023-01-10 14:54 ` Anthony Krowiak
2023-01-10 15:27 ` Christoph Hellwig
2023-01-10 15:32 ` Anthony Krowiak
2023-01-10 16:11 ` Jason Gunthorpe
2023-01-10 9:10 ` [PATCH 2/4] vfio-mdev: turn VFIO_MDEV into a selectable symbol Christoph Hellwig
2023-01-10 14:51 ` Anthony Krowiak
2023-01-10 16:12 ` Jason Gunthorpe
2023-01-10 9:10 ` [PATCH 3/4] vfio-mdev: move the mtty usage documentation Christoph Hellwig
2023-01-10 16:12 ` Jason Gunthorpe
2023-01-10 9:10 ` [PATCH 4/4] vfio-mdev: remove an non-existing driver from vfio-mediated-device Christoph Hellwig
2023-01-10 14:49 ` Anthony Krowiak [this message]
2023-01-10 16:13 ` Jason Gunthorpe
2023-01-23 19:37 ` misc mdev tidyups Alex Williamson
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=625de375-562d-3a72-830b-4c4835ab93e6@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox