From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH] maintainers: fix responsibility of flow API bits
Date: Tue, 15 May 2018 18:23:03 +0200 [thread overview]
Message-ID: <20180515162211.7030-1-adrien.mazarguil@6wind.com> (raw)
In-Reply-To: <1525944544-13513-1-git-send-email-bernard.iremonger@intel.com>
The following commits lack MAINTAINERS entries for this mess.
Fixes: 4d73b6fb9907 ("doc: add generic flow API guide")
Fixes: 19c90af6285c ("app/testpmd: add flow command")
Cc: stable@dpdk.org
Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index bd08d4292..187817fff 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -303,6 +303,8 @@ F: devtools/test-null.sh
Flow API
M: Adrien Mazarguil <adrien.mazarguil@6wind.com>
T: git://dpdk.org/next/dpdk-next-net
+F: app/test-pmd/cmdline_flow.c
+F: doc/guides/prog_guide/rte_flow.rst
F: lib/librte_ethdev/rte_flow*
Traffic Management API - EXPERIMENTAL
--
2.11.0
next prev parent reply other threads:[~2018-05-15 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 9:29 [dpdk-dev] [PATCH] maintainers: add maintainer for testpmd Bernard Iremonger
2018-05-15 16:23 ` Adrien Mazarguil [this message]
2018-05-16 9:18 ` [dpdk-dev] [PATCH] maintainers: fix responsibility of flow API bits Iremonger, Bernard
2018-05-16 14:35 ` Adrien Mazarguil
2018-05-17 9:26 ` Iremonger, Bernard
2018-05-17 11:20 ` Adrien Mazarguil
2018-05-17 11:26 ` Iremonger, Bernard
2018-05-17 14:45 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2018-05-17 14:51 ` Iremonger, Bernard
2018-05-17 15:50 ` Adrien Mazarguil
2018-05-16 0:44 ` [dpdk-dev] [PATCH] maintainers: add maintainer for testpmd Lu, Wenzhuo
2018-05-22 20:54 ` 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=20180515162211.7030-1-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).