From: Alex Williamson <alex.williamson@redhat.com>
To: Yishai Hadas <yishaih@nvidia.com>
Cc: <linux-kernel@vger.kernel.org>, <jgg@nvidia.com>,
<shameerali.kolothum.thodi@huawei.com>, <kevin.tian@intel.com>,
<linux-doc@vger.kernel.org>, <corbet@lwn.net>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers
Date: Mon, 14 Mar 2022 13:17:38 -0600 [thread overview]
Message-ID: <20220314131738.146c3e79.alex.williamson@redhat.com> (raw)
In-Reply-To: <a635abc8-be36-a9ee-dd8b-2950cc368562@nvidia.com>
On Mon, 14 Mar 2022 21:07:01 +0200
Yishai Hadas <yishaih@nvidia.com> wrote:
> On 3/14/2022 6:09 PM, Alex Williamson wrote:
> > 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>
> > ---
> >
> > Per the proposal here[1], I've collected those that volunteered and
> > those that I interpreted as showing interest (alpha by last name). For
> > those on the reviewers list below, please R-b/A-b to keep your name as a
> > reviewer. More volunteers are still welcome, please let me know
> > explicitly; R-b/A-b will not be used to automatically add reviewers but
> > are of course welcome. Thanks,
>
> You can add me as well to the reviewers list.
Thanks, Yishai! v2 posted including you, please send ack or review.
Thanks,
Alex
next prev parent reply other threads:[~2022-03-14 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 16:09 Alex Williamson
2022-03-14 19:07 ` Yishai Hadas
2022-03-14 19:17 ` Alex Williamson [this message]
2022-03-15 7:41 ` Christoph Hellwig
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=20220314131738.146c3e79.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=corbet@lwn.net \
--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
all inboxes | Powered by JetHome®