mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Song <xinmengs@nvidia.com>
To: Alex Williamson <alex@shazbot.org>
Cc: jgg@nvidia.com, dakr@kernel.org, acourbot@nvidia.com,
	yishaih@nvidia.com, skolothumtho@nvidia.com,
	kevin.tian@intel.com, jhubbard@nvidia.com, ecourtney@nvidia.com,
	cjia@nvidia.com, smitra@nvidia.com, kjaju@nvidia.com,
	alkumar@nvidia.com, ankita@nvidia.com, aniketa@nvidia.com,
	kwankhede@nvidia.com, targupta@nvidia.com,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	zhiwang@kernel.org, zhiw@nvidia.com
Subject: Re: [PATCH v3 0/1] vfio/pci: Give drivers control of PCI driver_data
Date: Tue, 13 Oct 2026 10:30:34 -0400	[thread overview]
Message-ID: <0438ee57-0597-43c2-a1e8-810fc82780b0@nvidia.com> (raw)
In-Reply-To: <20261010134826.55364f0f@shazbot.org>

On 10/10/2026 3:48 PM, Alex Williamson wrote:

> 
> I pulled in Dave's topic/pci-vgaarb-rework-2026-10-01, which gives us
> 93d41424caf7.  The vfio_pci_core_device is now registered with the vga
> client so we no longer need to derive anything from the pci_dev.  This
> makes all the VGA changes here unnecessary.
> 
> Applied to vfio next branch for v7.4 with the VGA chunks (shown in
> the discussion thread) and commit log paragraph describing them dropped.
> Thanks,
> 
> Alex


Hi Alex,

Thanks for applying this and handling the rebase, dropping the VGA change looks good with Dave's change.

Thanks also to Jason and Danilo for the reviews.

Simon

      reply	other threads:[~2026-10-13 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 18:42 Simon Song
2026-10-05 18:42 ` [PATCH v3 1/1] vfio/pci: Remove the core dependency on driver data Simon Song
2026-10-05 19:21   ` Danilo Krummrich
2026-10-09 19:28   ` Jason Gunthorpe
2026-10-09 21:18     ` Alex Williamson
2026-10-10 10:41       ` Danilo Krummrich
2026-10-10 19:48 ` [PATCH v3 0/1] vfio/pci: Give drivers control of PCI driver_data Alex Williamson
2026-10-13 14:30   ` Simon Song [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=0438ee57-0597-43c2-a1e8-810fc82780b0@nvidia.com \
    --to=xinmengs@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=alex@shazbot.org \
    --cc=alkumar@nvidia.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=cjia@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=ecourtney@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kjaju@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skolothumtho@nvidia.com \
    --cc=smitra@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=yishaih@nvidia.com \
    --cc=zhiw@nvidia.com \
    --cc=zhiwang@kernel.org \
    /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®