Mark librte_meter and librte_sched as being handled in the dpdk-next-qos subtree. The packet framework bits go through dpdk-next-pipeline.
Signed-off-by: David Marchand <david.march...@redhat.com> --- MAINTAINERS | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index b0cd0440ef..429b47003e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1256,6 +1256,7 @@ F: doc/guides/sample_app_ug/packet_ordering.rst Hierarchical scheduler M: Cristian Dumitrescu <cristian.dumitre...@intel.com> M: Jasvinder Singh <jasvinder.si...@intel.com> +T: git://dpdk.org/next/dpdk-next-qos F: lib/librte_sched/ F: doc/guides/prog_guide/qos_framework.rst F: app/test/test_red.c @@ -1275,6 +1276,7 @@ F: doc/guides/tools/pdump.rst Packet Framework ---------------- M: Cristian Dumitrescu <cristian.dumitre...@intel.com> +T: git://dpdk.org/next/dpdk-next-pipeline F: lib/librte_pipeline/ F: lib/librte_port/ F: lib/librte_table/ @@ -1341,6 +1343,7 @@ F: app/test/test_fib* Traffic metering M: Cristian Dumitrescu <cristian.dumitre...@intel.com> +T: git://dpdk.org/next/dpdk-next-qos F: lib/librte_meter/ F: doc/guides/sample_app_ug/qos_scheduler.rst F: app/test/test_meter.c -- 2.23.0
