From: Pankaj Gupta <pagupta@vmware.com>
To: jbehrens@vmware.com
Cc: dev@dpdk.org, pagupta@vmware.com
Subject: [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6
Date: Tue, 24 May 2022 17:40:19 -0700 [thread overview]
Message-ID: <20220525004028.24938-1-pagupta@vmware.com> (raw)
v6 (Andrew Rybchenko):
Minor style changes in patches description
Split FW version get patch to have callbacks reorder seperately
Minor fix in FW version get patch to put callback definition,
assignment and implementation just after device info get
v5:
Use RTE_MIN instead of defining MIN in drivers/net/vmxnet3/vmxnet3_ethdev.c
User RETA instead of reta in commit message
Fix the issue thrown by checkpatches.sh in file drivers/net/vmxnet3/vmxnet3_ethdev.c
v4:
Changing the subject for [Patch 8/8] from "net/vmxnet3: fix merge error
in initialization for rxDataRing feature" to
"Fixes: 046f11619567 ("net/vmxnet3: support MSI-X interrupt")"
v3:
adding Reviewed-by info in all the patches
v2:
address review comments from Andrew Rybchenko andrew.rybchenko@oktetlabs.ru
Pankaj Gupta (9):
net/vmxnet3: add version 5 support
net/vmxnet3: implement RETA query and RETA update
net/vmxnet3: add Rx queue usage count utility
net/vmxnet3: fix ethdev callbacks init order
net/vmxnet3: report HW version on FW version get
net/vmxnet3: add version 6 support
net/vmxnet3: advertise RETA size in device info
net/vmxnet3: set packet type for fragmented packet
net/vmxnet3: fix merge error in Rx data ring initialization
doc/guides/rel_notes/release_21_08.rst | 12 +
drivers/net/vmxnet3/base/vmxnet3_defs.h | 73 ++++-
drivers/net/vmxnet3/vmxnet3_ethdev.c | 339 +++++++++++++++++++-----
drivers/net/vmxnet3/vmxnet3_ethdev.h | 15 +-
drivers/net/vmxnet3/vmxnet3_rxtx.c | 49 +++-
5 files changed, 400 insertions(+), 88 deletions(-)
--
2.17.1
next reply other threads:[~2022-05-25 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 0:40 Pankaj Gupta [this message]
2022-05-25 0:40 ` [PATCH v6 1/9] net/vmxnet3: add version 5 support Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 2/9] net/vmxnet3: implement RETA query and RETA update Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 3/9] net/vmxnet3: add Rx queue usage count utility Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 4/9] net/vmxnet3: fix ethdev callbacks init order Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 5/9] net/vmxnet3: report HW version on FW version get Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 6/9] net/vmxnet3: add version 6 support Pankaj Gupta
2022-05-25 8:45 ` Andrew Rybchenko
2022-05-25 17:13 ` Pankaj Gupta
2022-05-31 12:54 ` Andrew Rybchenko
2022-05-25 0:40 ` [PATCH v6 7/9] net/vmxnet3: advertise RETA size in device info Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 8/9] net/vmxnet3: set packet type for fragmented packet Pankaj Gupta
2022-05-25 0:40 ` [PATCH v6 9/9] net/vmxnet3: fix merge error in Rx data ring initialization Pankaj Gupta
2022-05-31 13:40 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-31 13:41 ` Andrew Rybchenko
-- strict thread matches above, loose matches on Subject: below --
2022-05-03 4:22 [PATCH 0/8] vmxnet3 version V5 and V6 Pankaj Gupta
2022-05-19 8:04 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-19 8:07 ` Andrew Rybchenko
2022-05-23 20:56 ` Pankaj Gupta
2022-05-24 6:46 ` Andrew Rybchenko
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=20220525004028.24938-1-pagupta@vmware.com \
--to=pagupta@vmware.com \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.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;
as well as URLs for NNTP newsgroup(s).