From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com, ferruh.yigit@intel.com
Subject: [dpdk-dev] [PATCH 0/3] net definitions fixes
Date: Wed, 23 Oct 2019 10:51:55 +0200 [thread overview]
Message-ID: <1571820718-7021-1-git-send-email-david.marchand@redhat.com> (raw)
Small patchset with fixes after inspecting the librte_net.
I copied stable@dpdk.org in the 2nd patch for information only.
--
David Marchand
David Marchand (3):
net: add missing rte prefix on PPPoE defines
net: add rte prefix to MPLS structure
net: hide internal CRC defines
lib/librte_net/rte_ether.h | 4 ++--
lib/librte_net/rte_mpls.h | 2 +-
lib/librte_net/rte_net.c | 4 ++--
lib/librte_net/rte_net_crc.c | 6 ++++++
lib/librte_net/rte_net_crc.h | 6 ------
lib/librte_pipeline/rte_table_action.c | 4 ++--
6 files changed, 13 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-10-23 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 8:51 David Marchand [this message]
2019-10-23 8:51 ` [dpdk-dev] [PATCH 1/3] net: add missing rte prefix on PPPoE defines David Marchand
2019-10-23 8:51 ` [dpdk-dev] [PATCH 2/3] net: add rte prefix to MPLS structure David Marchand
2019-10-23 8:51 ` [dpdk-dev] [PATCH 3/3] net: hide internal CRC defines David Marchand
2019-10-23 12:12 ` [dpdk-dev] [PATCH 0/3] net definitions fixes Ferruh Yigit
2019-10-23 12:57 ` David Marchand
2019-10-23 13:00 ` David Marchand
2019-10-23 13:19 ` Ferruh Yigit
2019-10-23 13:39 ` [dpdk-dev] [PATCH v2 0/4] " David Marchand
2019-10-23 13:39 ` [dpdk-dev] [PATCH v2 1/4] doc: add note on prefixing ESP tail structure David Marchand
2019-10-23 13:39 ` [dpdk-dev] [PATCH v2 2/4] net: add missing rte prefix on PPPoE defines David Marchand
2019-10-23 13:40 ` [dpdk-dev] [PATCH v2 3/4] net: add rte prefix to MPLS structure David Marchand
2019-10-23 13:40 ` [dpdk-dev] [PATCH v2 4/4] net: hide internal CRC defines David Marchand
2019-10-23 20:03 ` [dpdk-dev] [PATCH v2 0/4] net definitions 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=1571820718-7021-1-git-send-email-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.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).