From: Michal Krawczyk <mk@semihalf.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, gtzalik@amazon.com, matua@amazon.com,
mw@semihalf.com, igorch@amazon.com,
Michal Krawczyk <mk@semihalf.com>
Subject: [dpdk-dev] [PATCH v2] net/ena: update version to 2.0.1
Date: Tue, 16 Jul 2019 12:59:56 +0200 [thread overview]
Message-ID: <20190716105956.15827-1-mk@semihalf.com> (raw)
In-Reply-To: <3e6798aa-d4d7-b3fb-5afa-bffdb0c64344@intel.com>
In 2.0.1 ENA, there were patches for:
* assigning NUMA node to the IO queue
- 4217cb0b7d2c ("net/ena: fix assigning NUMA node to IO queue")
* statistics counters (Rx checksum errors and per-queue number of the
Tx packets)
- ef74b5f7b69b ("net/ena: fix Rx checksum errors statistics")
- 5673e285a633 ("net/ena: fix Tx statistics")
* SMP support
- 117ba4a60488 ("net/ena: get device info statically")
* setting Rx checksum support
- ef538c1a7f56 ("net/ena: fix checksum feature flag")
Signed-off-by: Michal Krawczyk <mk@semihalf.com>
---
v2:
* Added list of commits being part of v2.0.1 to the commit message
drivers/net/ena/ena_ethdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
index f58334080..a1187851c 100644
--- a/drivers/net/ena/ena_ethdev.c
+++ b/drivers/net/ena/ena_ethdev.c
@@ -55,7 +55,7 @@
#define DRV_MODULE_VER_MAJOR 2
#define DRV_MODULE_VER_MINOR 0
-#define DRV_MODULE_VER_SUBMINOR 0
+#define DRV_MODULE_VER_SUBMINOR 1
#define ENA_IO_TXQ_IDX(q) (2 * (q))
#define ENA_IO_RXQ_IDX(q) (2 * (q) + 1)
--
2.20.1
next prev parent reply other threads:[~2019-07-16 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 8:16 [dpdk-dev] [PATCH] " Michal Krawczyk
2019-07-16 8:55 ` Ferruh Yigit
2019-07-16 10:59 ` Michal Krawczyk [this message]
2019-07-16 11:13 ` [dpdk-dev] [PATCH v3] " Michal Krawczyk
2019-07-16 20:22 ` Ferruh Yigit
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=20190716105956.15827-1-mk@semihalf.com \
--to=mk@semihalf.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=matua@amazon.com \
--cc=mw@semihalf.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).