From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Jerin Jacob <jerinjacobk@gmail.com>,
David Marchand <david.marchand@redhat.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
"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 09:54:44 +0000 [thread overview]
Message-ID: <17dc2e968d8040828cd3df120669980a@pantheon.tech> (raw)
In-Reply-To: <CALBAE1Nsor3BMdmYGeeHEBJGtrnVXR0DjzjTTrLRwmCQYY0e5A@mail.gmail.com>
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Thursday, April 29, 2021 11:23 AM
> To: David Marchand <david.marchand@redhat.com>; Juraj Linkeš
> <juraj.linkes@pantheon.tech>
> Cc: dpdk-dev <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>;
> 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
>
> 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?
>
> > ---
> > config/arm/meson.build | 19 +++++++++++++++++++
> > .../linux_gsg/cross_build_dpdk_for_arm64.rst | 18 +++++-------------
> > 2 files changed, 24 insertions(+), 13 deletions(-)
> >
> > diff --git a/config/arm/meson.build b/config/arm/meson.build index
> > 22cd81319c..fbe942e5ec 100644
> > --- a/config/arm/meson.build
> > +++ b/config/arm/meson.build
> > @@ -321,6 +321,25 @@ soc_thunderxt88 = {
> > 'part_number': '0xa1'
> > }
> >
> > +# Keep this part in sync with the socs list below:
> > +#
> > +# #guide_doc Start of socs list
> > +# generic: Generic un-optimized build for all aarch64 machines.
> > +# armada: Marvell ARMADA
> > +# bluefield: NVIDIA BlueField
> > +# cn10k: Marvell OCTEON 10
> > +# dpaa: NXP DPAA
> > +# emag: Ampere eMAG
> > +# graviton2: AWS Graviton2
> > +# kunpeng920: HiSilicon Kunpeng 920
> > +# kunpeng930: HiSilicon Kunpeng 930
> > +# n1sdp: Arm Neoverse N1SDP
> > +# n2: Arm Neoverse N2
> > +# octeontx2: Marvell OCTEON TX2
> > +# stingray: Broadcom Stingray
> > +# thunderx2: Marvell ThunderX2 T99
> > +# thunderxt88: Marvell ThunderX T88
> > +# #guide_doc End of socs list
> > socs = {
> > 'generic': soc_generic,
> > 'armada': soc_armada,
> > diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> > b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> > index 3857cdefe9..958bc81784 100644
> > --- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> > +++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> > @@ -197,19 +197,11 @@ option::
> >
> > meson soc_build -Dplatform=<target_soc>
> >
> > -Substitute <target_soc> with one of the supported SoCs::
> > -
> > - generic: Generic un-optimized build for all aarch64 machines.
> > - armada: Marvell ARMADA
> > - bluefield: NVIDIA BlueField
> > - dpaa: NXP DPAA
> > - emag: Ampere eMAG
> > - graviton2: AWS Graviton2
> > - n1sdp: Arm Neoverse N1SDP
> > - octeontx2: Marvell OCTEON TX2
> > - stingray: Broadcom Stingray
> > - thunderx2: Marvell ThunderX2 T99
> > - thunderxt88: Marvell ThunderX T88
> > +Substitute <target_soc> with one of the supported SoCs
> > +
> > +.. literalinclude:: ../../../config/arm/meson.build
> > + :start-after: #guide_doc Start of socs list
> > + :end-before: #guide_doc End of socs list
> >
> > These SoCs are also used in cross files, e.g.::
> >
> > --
> > 2.23.0
> >
next prev parent reply other threads:[~2021-04-29 9:54 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š [this message]
2021-04-29 11:41 ` Thomas Monjalon
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=17dc2e968d8040828cd3df120669980a@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=ndabilpuram@marvell.com \
--cc=oulijun@huawei.com \
--cc=pbhagavatula@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=tangchengchang@huawei.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).