All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuying Zhang <yuying.zhang@intel.com>
To: dev@dpdk.org, ferruh.yigit@intel.com, xiaoyun.li@intel.com,
	cristian.dumitrescu@intel.com, thomas@monjalon.net
Cc: Yuying Zhang <yuying.zhang@intel.com>
Subject: [PATCH v1] maintainers: update for testpmd
Date: Wed,  9 Feb 2022 15:01:05 +0000	[thread overview]
Message-ID: <20220209150105.1005313-1-yuying.zhang@intel.com> (raw)

Add Cristian as maintainer of test-pmd/cmdline_tm.* files.

Signed-off-by: Yuying Zhang <yuying.zhang@intel.com>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index c65b753c6b..cab1821b11 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -406,6 +406,7 @@ F: lib/ethdev/rte_flow*
 Traffic Management API - EXPERIMENTAL
 M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
 T: git://dpdk.org/next/dpdk-next-net
+F: app/test-pmd/cmdline_tm.*
 F: lib/ethdev/rte_tm*
 
 Traffic Metering and Policing API - EXPERIMENTAL
-- 
2.25.1


             reply	other threads:[~2022-02-09  7:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 15:01 Yuying Zhang [this message]
2022-02-09  9:23 ` [PATCH v1] maintainers: update for testpmd Dumitrescu, Cristian
2022-02-09 14:12   ` Ferruh Yigit
2022-02-09 14:27 ` Ferruh Yigit
2022-02-10 14:51 ` [PATCH v3] " Yuying Zhang
2022-02-10 14:58   ` Ferruh Yigit
2022-02-24 13:15   ` Dumitrescu, Cristian
2022-03-08 22:42     ` Thomas Monjalon
2022-02-10 17:11 ` [PATCH v2] " Yuying Zhang
2022-02-10 10:09   ` Ferruh Yigit
  -- strict thread matches above, loose matches on Subject: below --
2022-02-09 17:28 [PATCH v1] " Yuying Zhang
2022-02-09 14:13 ` Ferruh Yigit
2022-01-07 16:54 Yuying Zhang
2022-01-07  9:10 ` Li, Xiaoyun
2022-01-10 14:37   ` Ferruh Yigit
2022-01-11 15:31     ` 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=20220209150105.1005313-1-yuying.zhang@intel.com \
    --to=yuying.zhang@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    --cc=xiaoyun.li@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.