From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@intel.com,
arybchenko@solarflare.com,
Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: [dpdk-dev] [PATCH 2/2] mbuf: fix missing Tx outer UDP checksum flag name
Date: Fri, 12 Oct 2018 01:04:39 +0530 [thread overview]
Message-ID: <20181011193440.31995-2-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <20181011193440.31995-1-jerin.jacob@caviumnetworks.com>
From: Nithin Dabilpuram <ndabilpuram@marvell.com>
Fix missing Tx outer udp checksum flag name
Fixes: e1b1ae51877c ("ethdev: add Tx offload outer UDP checksum definition")
Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
This patch is based on next-net tree. We could stash this patch.
---
lib/librte_mbuf/rte_mbuf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_mbuf/rte_mbuf.c b/lib/librte_mbuf/rte_mbuf.c
index a93995184..fb741f06b 100644
--- a/lib/librte_mbuf/rte_mbuf.c
+++ b/lib/librte_mbuf/rte_mbuf.c
@@ -409,6 +409,7 @@ const char *rte_get_tx_ol_flag_name(uint64_t mask)
case PKT_TX_MACSEC: return "PKT_TX_MACSEC";
case PKT_TX_SEC_OFFLOAD: return "PKT_TX_SEC_OFFLOAD";
case PKT_TX_UDP_SEG: return "PKT_TX_UDP_SEG";
+ case PKT_TX_OUTER_UDP_CKSUM: return "PKT_TX_OUTER_UDP_CKSUM";
default: return NULL;
}
}
--
2.19.1
next prev parent reply other threads:[~2018-10-11 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 19:34 [dpdk-dev] [PATCH 1/2] mbuf: fix missing Tx offload flag name and list update Jerin Jacob
2018-10-11 19:34 ` Jerin Jacob [this message]
2018-10-12 11:25 ` Ferruh Yigit
2018-10-16 12:45 ` [dpdk-dev] [PATCH v2 " Jerin Jacob
2018-10-16 12:45 ` [dpdk-dev] [PATCH v2 2/2] mbuf: fix missing Tx outer UDP checksum flag name Jerin Jacob
2018-10-16 13:42 ` [dpdk-dev] [PATCH v2 1/2] mbuf: fix missing Tx offload flag name and list update Ferruh Yigit
2018-10-16 13:55 ` 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=20181011193440.31995-2-jerin.jacob@caviumnetworks.com \
--to=jerin.jacob@caviumnetworks.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
/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).