DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuying Zhang <yuying.zhang@intel.com>
To: dev@dpdk.org, xiaoyun.li@intel.com, ferruh.yigit@intel.com,
	thomas@monjalon.net, konstantin.ananyev@intel.com
Cc: Yuying Zhang <yuying.zhang@intel.com>
Subject: [PATCH v2] maintainers: update for testpmd
Date: Thu, 10 Feb 2022 15:03:38 +0000	[thread overview]
Message-ID: <20220210150338.1064314-1-yuying.zhang@intel.com> (raw)
In-Reply-To: <20220209172806.1009012-1-yuying.zhang@intel.com>

Move 'test-pmd/bpf_cmd.*' files under BPF component.

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

diff --git a/MAINTAINERS b/MAINTAINERS
index c65b753c6b..bdbf2f9e7f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1616,6 +1616,7 @@ F: lib/bpf/
 F: examples/bpf/
 F: app/test/test_bpf.c
 F: doc/guides/prog_guide/bpf_lib.rst
+F: app/test-pmd/bpf_cmd.*
 
 Graph - EXPERIMENTAL
 M: Jerin Jacob <jerinj@marvell.com>
-- 
2.25.1


  parent reply	other threads:[~2022-02-10 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 17:28 [PATCH v1] " Yuying Zhang
2022-02-09 14:13 ` Ferruh Yigit
2022-02-10 15:03 ` Yuying Zhang [this message]
2022-03-08 22:48   ` [PATCH v2] " Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2022-02-09 15:01 [PATCH v1] " Yuying Zhang
2022-02-10 17:11 ` [PATCH v2] " Yuying Zhang
2022-02-10 10:09   ` Ferruh Yigit
2021-10-22  7:19 [dpdk-dev] [PATCH] maintainers: update for driver testing tool Aman Singh
2021-11-25 10:01 ` [PATCH v2] maintainers: update for testpmd Thomas Monjalon
2021-11-25 13:40   ` Ferruh Yigit
2021-11-25 15:20     ` Thomas Monjalon
2021-11-25 16:04       ` Ferruh Yigit
2021-11-25 16:31         ` Ferruh Yigit
2021-11-25 16:56           ` 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=20220210150338.1064314-1-yuying.zhang@intel.com \
    --to=yuying.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@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 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).