Linux Documentation
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
	yishaih@nvidia.com, linux-doc@vger.kernel.org, corbet@lwn.net,
	hch@infradead.org
Subject: Re: [PATCH v4] vfio-pci: Provide reviewers and acceptance criteria for variant drivers
Date: Tue, 15 Mar 2022 14:50:39 -0300	[thread overview]
Message-ID: <20220315175039.GL11336@nvidia.com> (raw)
In-Reply-To: <164736509088.181560.2887686123582116702.stgit@omen>

On Tue, Mar 15, 2022 at 11:29:57AM -0600, Alex Williamson wrote:
> 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>
> Acked-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> Reviewed-by: Yishai Hadas <yishaih@nvidia.com>
> Acked-by: Kevin Tian <kevin.tian@intel.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> 
> v4:
> 
> Banish the word "vendor", replace with "device specific"
> Minor wording changes in docs file
> Add sign-offs from Kevin and Yishai
> 
> I'll drop Jason from reviewers if there's no positive approval
> after this round.

Sorry, you are looking for this?

Acked-by: Jason Gunthorpe <jgg@nvidia.com>

Thanks,
Jason

  parent reply	other threads:[~2022-03-15 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 17:29 [PATCH v4] vfio-pci: Provide reviewers and acceptance criteria for variant drivers Alex Williamson
2022-03-15 17:40 ` Cornelia Huck
2022-03-15 17:50 ` Jason Gunthorpe [this message]
2022-03-15 17:57   ` Alex Williamson
2022-03-16 21:10 ` Jonathan Corbet
2022-03-16 21:12   ` Alex Williamson
2022-03-17 16:03 ` 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=20220315175039.GL11336@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=corbet@lwn.net \
    --cc=hch@infradead.org \
    --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