From: sashiko-bot@kernel.org
To: "Lukasz Laguna" <lukasz.laguna@intel.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 13/13] drm/xe/pf: Use pci_iov_get_virtfn()
Date: Mon, 19 Oct 2026 08:43:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-176829@kernel.org> (raw)
In-Reply-To: <20261019083514.838640-14-lukasz.laguna@intel.com>
> xe_pci_sriov_get_vf_pdev() implements its own VF lookup. Replace it with
> pci_iov_get_virtfn(), which also takes the VF's bus number into account.
> Previously, the VF was assumed to be on the PF's bus, which is not always
> true.
>
> Signed-off-by: Lukasz Laguna <lukasz.laguna@intel.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261019083514.838640-1-lukasz.laguna@intel.com?part=13
prev parent reply other threads:[~2026-10-19 8:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 8:35 [PATCH v1 00/13] PCI/IOV: Improve reset handling with VFs enabled Lukasz Laguna
2026-10-19 8:35 ` [PATCH v1 01/13] PCI/IOV: Introduce pci_iov_get_virtfn() Lukasz Laguna
2026-10-19 8:43 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 02/13] PCI/IOV: Introduce VF iterators Lukasz Laguna
2026-10-19 8:43 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 03/13] PCI/IOV: Introduce VF locking helpers Lukasz Laguna
2026-10-19 8:47 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 04/13] PCI/IOV: Allow VF drivers to handle resets Lukasz Laguna
2026-10-19 9:03 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 05/13] ionic: Lock VFs around pci_reset_function_locked() Lukasz Laguna
2026-10-19 8:45 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 06/13] pds_core: " Lukasz Laguna
2026-10-19 8:44 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 07/13] i40e: Drop VF MSI state restore from PF reset_done Lukasz Laguna
2026-10-19 8:42 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 08/13] PCI/IOV: Allow bus reset_method for PF with VFs enabled Lukasz Laguna
2026-10-19 8:48 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 09/13] PCI/TSM: Use generic VF iterators Lukasz Laguna
2026-10-19 8:40 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 10/13] ixgbe: Use generic VF iterator Lukasz Laguna
2026-10-19 8:41 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 11/13] ice: Use pci_iov_get_virtfn() Lukasz Laguna
2026-10-19 8:42 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 12/13] liquidio: " Lukasz Laguna
2026-10-19 8:43 ` sashiko-bot
2026-10-19 8:35 ` [PATCH v1 13/13] drm/xe/pf: " Lukasz Laguna
2026-10-19 8:43 ` sashiko-bot [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=sashiko-outbox-176829@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukasz.laguna@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.