From: Michal Krawczyk <mk@semihalf.com>
To: gtzalik@amazon.com, mw@semihalf.com, matua@amazon.com
Cc: rk@semihalf.com, dev@dpdk.org, Michal Krawczyk <mk@semihalf.com>
Subject: [dpdk-dev] [PATCH 0/5] net/ena: minor fixes and docs update
Date: Fri, 25 Jan 2019 09:10:23 +0100 [thread overview]
Message-ID: <1548403828-31870-1-git-send-email-mk@semihalf.com> (raw)
Hi,
we would like to push fixes for part of the bugs reported in Bug 193,
together with docs update for ENAv2 about enabling WC support, release
notes and fix for assigning rte_errno negative values, as requested by
the community.
Michal Krawczyk (3):
net/ena: remove lcore constraint from max queue number
net/ena: fix dev init for RTE_PROC_SECONDARY
net/ena: fix setting rte_errno to negative value
Rafal Kozik (2):
doc: update release notes for ENA PMD
doc: add instructions for enabling WC in ENAv2 PMD
doc/guides/nics/ena.rst | 16 ++++++++++++++--
doc/guides/rel_notes/release_19_02.rst | 19 +++++++++++++++++++
drivers/net/ena/ena_ethdev.c | 20 ++++++++++----------
3 files changed, 43 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-25 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 8:10 Michal Krawczyk [this message]
2019-01-25 8:10 ` [dpdk-dev] [PATCH 1/5] net/ena: remove lcore constraint from max queue number Michal Krawczyk
2019-01-25 8:10 ` [dpdk-dev] [PATCH 2/5] net/ena: fix dev init for RTE_PROC_SECONDARY Michal Krawczyk
2019-01-25 8:10 ` [dpdk-dev] [PATCH 3/5] net/ena: fix setting rte_errno to negative value Michal Krawczyk
2019-01-25 8:10 ` [dpdk-dev] [PATCH 4/5] doc: update release notes for ENA PMD Michal Krawczyk
2019-01-25 8:10 ` [dpdk-dev] [PATCH 5/5] doc: add instructions for enabling WC in ENAv2 PMD Michal Krawczyk
2019-01-27 22:45 ` [dpdk-dev] [PATCH 0/5] net/ena: minor fixes and docs update Thomas Monjalon
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=1548403828-31870-1-git-send-email-mk@semihalf.com \
--to=mk@semihalf.com \
--cc=dev@dpdk.org \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=mw@semihalf.com \
--cc=rk@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).