From: Eli Cohen <elic@nvidia.com>
To: <stephen@networkplumber.org>, <netdev@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>
Cc: <jasowang@redhat.com>, <mst@redhat.com>, <lulu@redhat.com>,
<si-wei.liu@oracle.com>, <parav@nvidia.com>,
Eli Cohen <elic@nvidia.com>
Subject: [PATCH v4 0/4] vdpa tool enhancements
Date: Wed, 2 Mar 2022 08:54:40 +0200 [thread overview]
Message-ID: <20220302065444.138615-1-elic@nvidia.com> (raw)
Hi Stephen,
this is a resend of v3 which omitted you and netdev from the recepient
list. I added a few "acked-by" and called it v4.
The following four patch series enhances vdpa to show negotiated
features for a vdpa device, max features for a management device and
allows to configure max number of virtqueue pairs.
v3->v4:
Resend the patches with added "Acked-by" to the right mailing list.
Eli Cohen (4):
vdpa: Remove unsupported command line option
vdpa: Allow for printing negotiated features of a device
vdpa: Support for configuring max VQ pairs for a device
vdpa: Support reading device features
vdpa/include/uapi/linux/vdpa.h | 4 +
vdpa/vdpa.c | 151 +++++++++++++++++++++++++++++++--
2 files changed, 148 insertions(+), 7 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-02 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 6:54 Eli Cohen [this message]
2022-03-02 6:54 ` [PATCH v4 1/4] vdpa: Remove unsupported command line option Eli Cohen
2022-03-09 8:59 ` Parav Pandit
2022-03-02 6:54 ` [PATCH v4 2/4] vdpa: Allow for printing negotiated features of a device Eli Cohen
2022-03-02 6:54 ` [PATCH v4 3/4] vdpa: Support for configuring max VQ pairs for " Eli Cohen
2022-03-09 8:58 ` Parav Pandit
2022-03-09 9:03 ` Eli Cohen
2022-03-09 9:06 ` Eli Cohen
2022-03-02 6:54 ` [PATCH v4 4/4] vdpa: Support reading device features Eli Cohen
2022-03-09 8:07 ` [PATCH v4 0/4] vdpa tool enhancements Jason Wang
2022-03-09 15:34 ` David Ahern
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=20220302065444.138615-1-elic@nvidia.com \
--to=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).