From: fengchengwen <fengchengwen@huawei.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] maintainers: assign some programming guides
Date: Tue, 12 Mar 2024 16:18:47 +0800 [thread overview]
Message-ID: <47ce262d-3501-40e8-5998-0e6a43e90000@huawei.com> (raw)
In-Reply-To: <20240308104113.3352313-1-david.marchand@redhat.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 2024/3/8 18:41, David Marchand wrote:
> Maintaining the documentation is part of the job of maintaining a library.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> MAINTAINERS | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4755a68274..12e21f78d1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -428,12 +428,14 @@ M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> T: git://dpdk.org/next/dpdk-next-net
> F: lib/ethdev/rte_tm*
> F: app/test-pmd/cmdline_tm.*
> +F: doc/guides/prog_guide/traffic_management.rst
>
> Traffic Metering and Policing API - EXPERIMENTAL
> M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> T: git://dpdk.org/next/dpdk-next-net
> F: lib/ethdev/rte_mtr*
> F: app/test-pmd/cmdline_mtr.*
> +F: doc/guides/prog_guide/traffic_metering_and_policing.rst
>
> Baseband API
> M: Nicolas Chautru <nicolas.chautru@intel.com>
> @@ -453,6 +455,7 @@ T: git://dpdk.org/next/dpdk-next-crypto
> F: lib/cryptodev/
> F: app/test/test_cryptodev*
> F: examples/l2fwd-crypto/
> +F: doc/guides/prog_guide/cryptodev_lib.rst
>
> Security API
> M: Akhil Goyal <gakhil@marvell.com>
> @@ -511,6 +514,7 @@ F: lib/eventdev/
> F: drivers/event/skeleton/
> F: app/test/test_eventdev.c
> F: examples/l3fwd/l3fwd_event*
> +F: doc/guides/prog_guide/eventdev.rst
>
> Eventdev Ethdev Rx Adapter API
> M: Naga Harish K S V <s.v.naga.harish.k@intel.com>
> @@ -1634,9 +1638,11 @@ RIB/FIB
> M: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> F: lib/rib/
> F: app/test/test_rib*
> +F: doc/guides/prog_guide/rib_lib.rst
> F: lib/fib/
> F: app/test/test_fib*
> F: app/test-fib/
> +F: doc/guides/prog_guide/fib_lib.rst
>
> Traffic metering
> M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> @@ -1654,6 +1660,7 @@ Argument parsing
> M: Chengwen Feng <fengchengwen@huawei.com>
> F: lib/argparse/
> F: app/test/test_argparse.c
> +F: doc/guides/prog_guide/argparse_lib.rst
>
> Configuration file
> M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> @@ -1719,6 +1726,7 @@ F: doc/guides/sample_app_ug/l2_forward_job_stats.rst
> Metrics
> F: lib/metrics/
> F: app/test/test_metrics.c
> +F: doc/guides/prog_guide/metrics_lib.rst
>
> Bit-rate statistics
> F: lib/bitratestats/
> @@ -1736,6 +1744,7 @@ F: app/test/test_telemetry*
> F: app/test/suites/test_telemetry.sh
> F: usertools/dpdk-telemetry*
> F: doc/guides/howto/telemetry.rst
> +F: doc/guides/prog_guide/telemetry_lib.rst
>
> BPF
> M: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
>
next prev parent reply other threads:[~2024-03-12 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 10:41 David Marchand
2024-03-12 8:18 ` fengchengwen [this message]
2024-03-18 3:35 ` 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=47ce262d-3501-40e8-5998-0e6a43e90000@huawei.com \
--to=fengchengwen@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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).