From: "Michael S. Tsirkin" <mst@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Ani Sinha <anisinha@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Sriram Yagnaraman <sriram.yagnaraman@est.tech>,
Jason Wang <jasowang@redhat.com>, Keith Busch <kbusch@kernel.org>,
Klaus Jensen <its@irrelevant.dk>
Subject: Re: [PATCH 0/3] pci: Fix ARI next function numbers
Date: Sun, 2 Jul 2023 04:44:10 -0400 [thread overview]
Message-ID: <20230702044103-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230702083357.13517-1-akihiko.odaki@daynix.com>
On Sun, Jul 02, 2023 at 05:33:53PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF. The PF should
> end the linked list formed with the field by specifying 0.
>
> Supersedes: <20230701070133.24877-1-akihiko.odaki@daynix.com>
> ("[PATCH 0/4] pci: Compare function number and ARI next function number")
changelog?
motivation?
effect on migration?
testing?
> Akihiko Odaki (3):
> docs: Fix next function numbers in SR/IOV documentation
> hw/nvme: Fix ARI next function numbers
> igb: Fix ARI next function numbers
>
> docs/pcie_sriov.txt | 4 ++--
> hw/net/igb.c | 2 +-
> hw/nvme/ctrl.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.41.0
next prev parent reply other threads:[~2023-07-02 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 8:33 [PATCH 0/3] pci: Fix ARI next function numbers Akihiko Odaki
2023-07-02 8:33 ` [PATCH 1/3] docs: Fix next function numbers in SR/IOV documentation Akihiko Odaki
2023-07-02 8:33 ` [PATCH 2/3] hw/nvme: Fix ARI next function numbers Akihiko Odaki
2023-07-02 8:33 ` [PATCH 3/3] igb: " Akihiko Odaki
2023-07-02 9:00 ` Michael S. Tsirkin
2023-07-02 9:49 ` Akihiko Odaki
2023-07-02 10:39 ` Michael S. Tsirkin
2023-07-02 8:44 ` Michael S. Tsirkin [this message]
2023-07-03 5:15 ` [PATCH 0/3] pci: " Ani Sinha
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=20230702044103-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=anisinha@redhat.com \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sriram.yagnaraman@est.tech \
/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;
as well as URLs for NNTP newsgroup(s).