From: Thomas Monjalon <thomas@monjalon.net>
To: "Jerin Jacob" <jerinjacobk@gmail.com>,
"David Marchand" <david.marchand@redhat.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Jan Viktorin <viktorin@rehivetech.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Lijun Ou <oulijun@huawei.com>,
Chengchang Tang <tangchengchang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix Arm socs list
Date: Thu, 29 Apr 2021 13:41:26 +0200 [thread overview]
Message-ID: <4253367.Dr5JuXj7qn@thomas> (raw)
In-Reply-To: <17dc2e968d8040828cd3df120669980a@pantheon.tech>
29/04/2021 11:54, Juraj Linkeš:
> From: Jerin Jacob <jerinjacobk@gmail.com>
> > On Thu, Apr 29, 2021 at 12:38 PM David Marchand
> > <david.marchand@redhat.com> wrote:
> > >
> > > Keep the list of socs in a single place and include it so that the
> > > documentation won't get outdated.
> > >
> > > Fixes: 1b4c86a721c9 ("config/arm: add Marvell CN10K")
> > > Fixes: 7cf32a22b240 ("config/arm: add Hisilicon kunpeng")
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> >
> > Reviewed-by: Jerin Jacob <jerinj@marvell.com>
> >
> > + @Juraj Linkeš
>
> Thanks for adding me.
>
> >
> > Could you enroll as maintainer for config/arm/meson.build file as most of the
> > change for this file done by you in the rework.
>
> Gladly, how do I do that? I didn't find anything about this in docs. Should I just submit a patch where I add myself to the MAINTAINERS file?
In general we avoid such fine granularity in MAINTAINERS.
This file is maintained as part of the ARM v8 area.
next prev parent reply other threads:[~2021-04-29 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 7:07 David Marchand
2021-04-29 9:22 ` Jerin Jacob
2021-04-29 9:54 ` Juraj Linkeš
2021-04-29 11:41 ` Thomas Monjalon [this message]
2021-04-29 9:53 ` Juraj Linkeš
2021-04-29 9:59 ` David Marchand
2021-04-29 14:56 ` Ruifeng Wang
2021-05-04 12:42 ` [dpdk-dev] [PATCH v2] " David Marchand
2021-05-05 20:46 ` 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=4253367.Dr5JuXj7qn@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=juraj.linkes@pantheon.tech \
--cc=ndabilpuram@marvell.com \
--cc=oulijun@huawei.com \
--cc=pbhagavatula@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=tangchengchang@huawei.com \
--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).