From: David Christensen <drc@linux.vnet.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: david.marchand@redhat.com, jerinj@marvell.com,
bruce.richardson@intel.com, ruifeng.wang@arm.com,
viktorin@rehivetech.com, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] maintainers: improve coverage of arch-specific files
Date: Tue, 6 Oct 2020 13:45:20 -0700 [thread overview]
Message-ID: <49ee9c3e-c966-ecfd-2fb6-3638f1a589dd@linux.vnet.ibm.com> (raw)
In-Reply-To: <20201006202250.3623749-1-thomas@monjalon.net>
On 10/6/20 1:22 PM, Thomas Monjalon wrote:
> The sub-directories of config/ are maintained by
> different architecture maintainers.
>
> Some wildcards are used to describe the lib and drivers files
> which are specific to some architectures.
>
> The EAL Arm files have split responsibilities depending on 32/64 suffix,
> and the common files are shared between Armv7 and Armv8 sections.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> MAINTAINERS | 23 +++++++++++------------
> 1 file changed, 11 insertions(+), 12 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 75a17d51c0..349fc9c38a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -256,32 +256,31 @@ F: app/test/test_rand_perf.c
> ARM v7
> M: Jan Viktorin <viktorin@rehivetech.com>
> M: Ruifeng Wang <ruifeng.wang@arm.com>
> +F: config/arm/
> F: lib/librte_eal/arm/
> +X: lib/librte_eal/arm/include/*_64.h
>
> ARM v8
> M: Jerin Jacob <jerinj@marvell.com>
> M: Ruifeng Wang <ruifeng.wang@arm.com>
> -F: lib/librte_eal/arm/include/*_64.h
> -F: lib/librte_net/net_crc_neon.h
> -F: lib/librte_acl/acl_run_neon.*
> -F: lib/librte_bpf/bpf_jit_arm64.c
> -F: lib/librte_lpm/rte_lpm_neon.h
> -F: lib/librte_hash/rte*_arm64.h
> -F: lib/librte_efd/rte*_arm64.h
> -F: lib/librte_table/rte*_arm64.h
> -F: drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c
> -F: drivers/net/i40e/i40e_rxtx_vec_neon.c
> -F: drivers/net/virtio/virtio_rxtx_simple_neon.c
> +F: config/arm/
> +F: lib/librte_eal/arm/
> +X: lib/librte_eal/arm/include/*_32.h
> +F: lib/*/*_neon.*
> +F: lib/*/*_arm64.*
> +F: drivers/*/*/*_neon.*
>
> IBM POWER (alpha)
> M: David Christensen <drc@linux.vnet.ibm.com>
> +F: config/ppc/
> F: lib/librte_eal/ppc/
> -F: drivers/net/i40e/i40e_rxtx_vec_altivec.c
> +F: drivers/*/*/*_altivec.*
> F: examples/l3fwd/*altivec.h
>
> Intel x86
> M: Bruce Richardson <bruce.richardson@intel.com>
> M: Konstantin Ananyev <konstantin.ananyev@intel.com>
> +F: config/x86/
> F: lib/librte_eal/x86/
>
> Linux EAL (with overlaps)
>
Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>
next prev parent reply other threads:[~2020-10-06 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 20:22 Thomas Monjalon
2020-10-06 20:45 ` David Christensen [this message]
2020-10-07 7:44 ` David Marchand
2020-10-07 10:06 ` Thomas Monjalon
2020-10-24 16:36 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-10-24 17:10 ` David Marchand
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=49ee9c3e-c966-ecfd-2fb6-3638f1a589dd@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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).