All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"aaronlewis@google.com" <aaronlewis@google.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"dmatlack@google.com" <dmatlack@google.com>,
	"vipinsh@google.com" <vipinsh@google.com>,
	"seanjc@google.com" <seanjc@google.com>,
	"jrhilke@google.com" <jrhilke@google.com>
Subject: Re: [PATCH] vfio/pci: Separate SR-IOV VF dev_set
Date: Tue, 15 Jul 2025 15:53:40 -0300	[thread overview]
Message-ID: <20250715185340.GS2067380@nvidia.com> (raw)
In-Reply-To: <20250715124223.67a36d2a.alex.williamson@redhat.com>

On Tue, Jul 15, 2025 at 12:42:23PM -0600, Alex Williamson wrote:

> I went ahead and added this to my next branch because I think your
> impression is that this is generally ok based on the vf-token, but if
> this raises new concerns I can drop it and we can discuss further.

Yeah, I think vf token will be good enough

Jason

      reply	other threads:[~2025-07-15 18:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 22:56 [PATCH] vfio/pci: Separate SR-IOV VF dev_set Alex Williamson
2025-06-30  6:32 ` Tian, Kevin
2025-06-30 13:15 ` Yi Liu
2025-06-30 14:57   ` Alex Williamson
2025-07-02 16:00 ` Jason Gunthorpe
2025-07-02 17:50   ` Alex Williamson
2025-07-02 17:55     ` Jason Gunthorpe
2025-07-03  6:10       ` Tian, Kevin
2025-07-03 13:23         ` Jason Gunthorpe
2025-07-03 20:29           ` Alex Williamson
2025-07-03 23:35             ` Jason Gunthorpe
2025-07-15 18:42               ` Alex Williamson
2025-07-15 18:53                 ` Jason Gunthorpe [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=20250715185340.GS2067380@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=aaronlewis@google.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dmatlack@google.com \
    --cc=jrhilke@google.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=vipinsh@google.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.