From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
oushixiong <oushixiong@kylinos.cn>,
Yishai Hadas <yishaih@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Brett Creeley <brett.creeley@amd.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vfio/pds: Use proper PF device access helper
Date: Mon, 18 Sep 2023 09:40:00 -0300 [thread overview]
Message-ID: <20230918124000.GB13795@ziepe.ca> (raw)
In-Reply-To: <BN9PR11MB527624CEBA0B039CD62A8F428CF5A@BN9PR11MB5276.namprd11.prod.outlook.com>
On Sat, Sep 16, 2023 at 09:53:29AM +0000, Tian, Kevin wrote:
> > From: Alex Williamson <alex.williamson@redhat.com>
> > Sent: Saturday, September 16, 2023 2:59 AM
> >
> > On Thu, 14 Sep 2023 10:13:32 +0800
> > oushixiong <oushixiong@kylinos.cn> wrote:
> >
> > > From: Shixiong Ou <oushixiong@kylinos.cn>
> > >
> > > The pci_physfn() helper exists to support cases where the physfn
> > > field may not be compiled into the pci_dev structure. We've
> > > declared this driver dependent on PCI_IOV to avoid this problem,
> > > but regardless we should follow the precedent not to access this
> > > field directly.
> > >
> > > Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
> > > ---
> > >
> > > This patch changes the subject line and commit log, and the previous
> > > patch's links is:
> > >
> > https://patchwork.kernel.org/project/kvm/patch/20230911080828.6
> > 35184-1-oushixiong@kylinos.cn/
> >
> > Kevin & Jason,
> >
> > I assume your R-b's apply to this version as well. Thanks,
> >
>
> yes.
yes
next prev parent reply other threads:[~2023-09-18 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 2:13 oushixiong
2023-09-14 17:31 ` Brett Creeley
2023-09-15 18:58 ` Alex Williamson
2023-09-16 9:53 ` Tian, Kevin
2023-09-18 12:40 ` Jason Gunthorpe [this message]
2023-09-18 20:51 ` 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=20230918124000.GB13795@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=brett.creeley@amd.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oushixiong@kylinos.cn \
--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
all inboxes | Powered by JetHome®