From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>, <stephen@networkplumber.org>
Subject: [PATCH v3 8/8] maintainers: update for kvargs library
Date: Tue, 22 Oct 2024 06:14:31 +0000 [thread overview]
Message-ID: <20241022061431.21925-9-fengchengwen@huawei.com> (raw)
In-Reply-To: <20241022061431.21925-1-fengchengwen@huawei.com>
Add myself for voluntary maintenance of the kvargs library.
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cd78bc7db1..f0bcebc651 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1718,6 +1718,7 @@ F: doc/guides/prog_guide/cmdline.rst
F: doc/guides/sample_app_ug/cmd_line.rst
Key/Value parsing
+M: Chengwen Feng <fengchengwen@huawei.com>
F: lib/kvargs/
F: app/test/test_kvargs.c
--
2.17.1
prev parent reply other threads:[~2024-10-22 6:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 9:53 [PATCH 0/7] refactor kvargs test Chengwen Feng
2023-11-03 9:53 ` [PATCH 1/7] app/test: introduce UT suite framework for kvargs Chengwen Feng
2024-10-11 2:08 ` Stephen Hemminger
2024-10-11 3:35 ` fengchengwen
2023-11-03 9:53 ` [PATCH 2/7] app/test: extract basic token count testcase " Chengwen Feng
2023-11-03 9:53 ` [PATCH 3/7] app/test: extract without keys " Chengwen Feng
2023-11-03 9:53 ` [PATCH 4/7] app/test: extract with " Chengwen Feng
2023-11-03 9:53 ` [PATCH 5/7] app/test: extract parse list value " Chengwen Feng
2023-11-03 9:53 ` [PATCH 6/7] app/test: extract parse empty elements " Chengwen Feng
2023-11-03 9:53 ` [PATCH 7/7] maintainers: update for kvargs library Chengwen Feng
2023-12-05 2:55 ` [PATCH 0/7] refactor kvargs test fengchengwen
2024-10-05 15:49 ` Stephen Hemminger
2024-10-11 3:34 ` [PATCH v2 " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 1/7] app/test: introduce UT suite framework for kvargs Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 2/7] app/test: extract basic token count testcase " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 3/7] app/test: extract without keys " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 4/7] app/test: extract with " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 5/7] app/test: extract parse list value " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 6/7] app/test: extract parse empty elements " Chengwen Feng
2024-10-11 3:34 ` [PATCH v2 7/7] maintainers: update for kvargs library Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 0/8] refactor kvargs test Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 1/8] app/test: introduce UT suite framework for kvargs Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 2/8] app/test: extract basic token count testcase " Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 3/8] app/test: extract without keys " Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 4/8] app/test: extract with " Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 5/8] app/test: extract parse list value " Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 6/8] app/test: extract parse empty elements " Chengwen Feng
2024-10-22 6:14 ` [PATCH v3 7/8] app/test: add process opt " Chengwen Feng
2024-10-22 6:14 ` Chengwen Feng [this message]
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=20241022061431.21925-9-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).