From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>,
Hyong Youb Kim <hyonkim@cisco.com>
Subject: [dpdk-dev] [PATCH 0/3] net/enic: minor bug fixes
Date: Sat, 20 Oct 2018 01:32:46 -0700 [thread overview]
Message-ID: <20181020083249.8187-1-hyonkim@cisco.com> (raw)
Fix a couple bugs found during internal testing, and update the
release notes, which was missing in previous patches.
The second patch ("net/enic: add missing Tx offload flags") addresses
a side effect from the following commit, which adds several previously
existing flags (e.g. PKT_TX_IPV4) to PKT_TX_OFFLOAD_MASK. The enic
driver, like a few other drivers, uses 'not-supported offload mask'
derived from PKT_TX_OFFLOAD_MASK to detect bad mbufs in
tx_pkt_prepare. And this mask needs an update to account for the added
flags. At least i40e is also affected.
commit ef28cfa73822 ("mbuf: fix Tx offload mask")
Hyong Youb Kim (3):
net/enic: fix supported packet types
net/enic: add missing Tx offload flags
doc: update release notes for the enic driver
doc/guides/rel_notes/release_18_11.rst | 7 +++++++
drivers/net/enic/enic_ethdev.c | 30 +++++++++++++++++++++++++++---
drivers/net/enic/enic_main.c | 6 ++----
drivers/net/enic/enic_res.c | 2 ++
4 files changed, 38 insertions(+), 7 deletions(-)
--
2.16.2
next reply other threads:[~2018-10-20 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 8:32 Hyong Youb Kim [this message]
2018-10-20 8:32 ` [dpdk-dev] [PATCH 1/3] net/enic: fix supported packet types Hyong Youb Kim
2018-10-22 14:20 ` Ferruh Yigit
2018-10-20 8:32 ` [dpdk-dev] [PATCH 2/3] net/enic: add missing Tx offload flags Hyong Youb Kim
2018-10-20 8:32 ` [dpdk-dev] [PATCH 3/3] doc: update release notes for the enic driver Hyong Youb Kim
2018-10-22 14:27 ` [dpdk-dev] [PATCH 0/3] net/enic: minor bug fixes 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=20181020083249.8187-1-hyonkim@cisco.com \
--to=hyonkim@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.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).