From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>,
<pasic@linux.ibm.com>, <cohuck@redhat.com>
Cc: <virtio-comment@lists.oasis-open.org>, <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH 0/2] transport-pci: msix register desc improve
Date: Thu, 20 Apr 2023 22:51:56 +0300 [thread overview]
Message-ID: <20230420195158.69737-1-parav@nvidia.com> (raw)
Problem:
Current wording queue_msix_vector and config_msix_vector says
"for MSI-X", which is bit confusing.
config_msix_vector and queue_msix_vector are the msix vector
number for configuration change and queue related interrupts.
Hence, reword it.
---
changelog:
v1->v2:
- rewrote to indicate MSI-X table entry index
v0->v1:
- added 'here'
- dropped 'receiving'
- dropped already merged patch for empty line
Parav Pandit (2):
transport-pci: Improve config msix vector description
transport-pci: Improve queue msix vector register desc
transport-pci.tex | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2023-04-20 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 19:51 Parav Pandit [this message]
2023-04-20 19:51 ` [virtio-dev] [PATCH 1/2] transport-pci: Improve config msix vector description Parav Pandit
2023-04-20 20:44 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-20 20:51 ` [virtio-dev] " Parav Pandit
2023-04-21 5:37 ` [virtio-dev] " Michael S. Tsirkin
2023-04-21 5:43 ` Michael S. Tsirkin
2023-04-20 19:51 ` [virtio-dev] [PATCH 2/2] transport-pci: Improve queue msix vector register desc Parav Pandit
2023-04-20 20:45 ` [virtio-dev] " Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2023-04-11 19:42 [virtio-dev] [PATCH 0/2] transport-pci: msix register desc improve Parav Pandit
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=20230420195158.69737-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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