mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v6.4-rc1
Date: Tue, 2 May 2023 12:46:25 -0600	[thread overview]
Message-ID: <20230502124625.355ec05e.alex.williamson@redhat.com> (raw)

Hi Linus,

The following changes since commit 09a9639e56c01c7a00d6c0ca63f4c7c41abe075d:

  Linux 6.3-rc6 (2023-04-09 11:15:57 -0700)

are available in the Git repository at:

  https://github.com/awilliam/linux-vfio.git tags/vfio-v6.4-rc1

for you to fetch changes up to 705b004ee377b789e39ae237519bab714297ac83:

  docs: kvm: vfio: Suggest KVM_DEV_VFIO_GROUP_ADD vs VFIO_GROUP_GET_DEVICE_FD ordering (2023-04-21 13:48:44 -0600)

----------------------------------------------------------------
VFIO updates for v6.4-rc1

 - Expose and allow R/W access to the PCIe DVSEC capability through
   vfio-pci, as we already do with the legacy vendor capability.
   (K V P Satyanarayana)

 - Fix kernel-doc issues with structure definitions. (Simon Horman)

 - Clarify ordering of operations relative to the kvm-vfio device for
   driver dependencies against the kvm pointer. (Yi Liu)

----------------------------------------------------------------
K V P, Satyanarayana (1):
      vfio/pci: Add DVSEC PCI Extended Config Capability to user visible list.

Simon Horman (1):
      vfio: correct kdoc for ops structures

Yi Liu (1):
      docs: kvm: vfio: Suggest KVM_DEV_VFIO_GROUP_ADD vs VFIO_GROUP_GET_DEVICE_FD ordering

 Documentation/virt/kvm/devices/vfio.rst | 5 +++++
 drivers/vfio/pci/vfio_pci_config.c      | 7 +++++++
 include/linux/vfio.h                    | 5 +++++
 3 files changed, 17 insertions(+)


             reply	other threads:[~2023-05-02 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 18:46 Alex Williamson [this message]
2023-05-02 19:03 ` pr-tracker-bot

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=20230502124625.355ec05e.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®