From: Si-Wei Liu <si-wei.liu@oracle.com>
To: mst@redhat.com, jasowang@redhat.com, elic@nvidia.com
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, si-wei.liu@oracle.com
Subject: [PATCH v3 0/1] mlx5_vdpa bug fix for feature negotiation
Date: Wed, 28 Apr 2021 21:48:53 -0400 [thread overview]
Message-ID: <1619660934-30910-1-git-send-email-si-wei.liu@oracle.com> (raw)
This v3 consisting of one single patch only is a follow-up
to the v2 of mlx5_vdpa bug fix series as in:
https://lore.kernel.org/virtualization/1612993680-29454-1-git-send-email-si-wei.liu@oracle.com
which initially attempted to fix a few independent issues in the
mlx5_vdpa driver.
Presently Patch #1 in the original series was piggybacked and got
merged through a separate patchset:
https://lore.kernel.org/virtualization/20210406170457.98481-13-parav@nvidia.com/
and the issue Patch #3 tried to fix was addressed by another patch,
https://lore.kernel.org/virtualization/a5356a13-6d7d-8086-bfff-ff869aec5449@redhat.com/
that leaves Patch #2 in the original v2 series unmerged. Since it
was already Ack'ed by Jason and Eli in v2, just get it reposted
while dropping others after syncing with the current vhost tree.
Thanks,
--
v2->v3: drop merged patches from previous series;
repost with updated commit message
v1->v2: move feature capability query to probing (Eli)
Si-Wei Liu (1):
vdpa/mlx5: fix feature negotiation across device reset
drivers/vdpa/mlx5/net/mlx5_vnet.c | 25 +++++++++++++++----------
1 file changed, 15 insertions(+), 10 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-04-29 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 1:48 Si-Wei Liu [this message]
2021-04-29 1:48 ` [PATCH v3 1/1] vdpa/mlx5: fix feature negotiation across device reset Si-Wei Liu
2021-08-26 0:00 ` Si-Wei Liu
2021-08-31 20:58 ` Si-Wei Liu
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=1619660934-30910-1-git-send-email-si-wei.liu@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).