From: Jonathan Corbet <corbet@lwn.net>
To: Alex Williamson <alex.williamson@redhat.com>,
alex.williamson@redhat.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jgg@nvidia.com,
shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
yishaih@nvidia.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers
Date: Mon, 14 Mar 2022 13:42:51 -0600 [thread overview]
Message-ID: <87pmmoxqv8.fsf@meer.lwn.net> (raw)
In-Reply-To: <164728518026.40450.7442813673746870904.stgit@omen>
Alex Williamson <alex.williamson@redhat.com> writes:
> Vendor or device specific extensions for devices exposed to userspace
> through the vfio-pci-core library open both new functionality and new
> risks. Here we attempt to provided formalized requirements and
> expectations to ensure that future drivers both collaborate in their
> interaction with existing host drivers, as well as receive additional
> reviews from community members with experience in this area.
>
> Cc: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Yishai Hadas <yishaih@nvidia.com>
> Cc: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> Cc: Kevin Tian <kevin.tian@intel.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
One thing...
> .../vfio/vfio-pci-vendor-driver-acceptance.rst | 35 ++++++++++++++++++++
> MAINTAINERS | 10 ++++++
> 2 files changed, 45 insertions(+)
If you add a new RST file, you need to add it to an index.rst somewhere
so that it becomes part of the kernel docs build.
Also, though: can we avoid creating a new top-level documentation
directory for just this file? It seems like it would logically be a
part of the maintainers guide (Documentation/maintainer) ... ?
Thanks,
jon
next prev parent reply other threads:[~2022-03-14 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:14 [PATCH v2] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers Alex Williamson
2022-03-14 19:32 ` Shameerali Kolothum Thodi
2022-03-14 19:42 ` Jonathan Corbet [this message]
2022-03-14 19:52 ` Alex Williamson
2022-03-14 19:58 ` Jonathan Corbet
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=87pmmoxqv8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alex.williamson@redhat.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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