From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Jan Viktorin <viktorin@rehivetech.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] maintainers: improve coverage of arch-specific files
Date: Sat, 24 Oct 2020 19:10:31 +0200 [thread overview]
Message-ID: <CAJFAV8zgwX+nVe1jvPftdoNVUGff_TRvda9fKokAHDQb9AUfiQ@mail.gmail.com> (raw)
In-Reply-To: <20201024163619.352920-1-thomas@monjalon.net>
On Sat, Oct 24, 2020 at 6:36 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> The sub-directories of config/ are maintained by
> different architecture maintainers.
>
> Some wildcards are used to describe the lib, drivers and app 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>
> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>
Squashed:
@@ -276,6 +276,7 @@ IBM POWER (alpha)
M: David Christensen <drc@linux.vnet.ibm.com>
F: config/ppc/
F: lib/librte_eal/ppc/
+F: lib/*/*_altivec*
F: drivers/*/*/*_altivec.*
F: app/*/*_altivec.*
F: examples/*/*_altivec.*
Acked-by: David Marchand <david.marchand@redhat.com>
Applied.
--
David Marchand
prev parent reply other threads:[~2020-10-24 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 20:22 [dpdk-dev] [PATCH] " Thomas Monjalon
2020-10-06 20:45 ` David Christensen
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 [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=CAJFAV8zgwX+nVe1jvPftdoNVUGff_TRvda9fKokAHDQb9AUfiQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--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).