From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH-V7] config/arm: add Qualcomm Centriq 2400 SoC config
Date: Thu, 13 May 2021 09:35:47 +0000 [thread overview]
Message-ID: <AM5PR0802MB24653C60403775439739BAC09E519@AM5PR0802MB2465.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20210507084815.25929-1-thierry.herbelot@6wind.com>
> -----Original Message-----
> From: Thierry Herbelot <thierry.herbelot@6wind.com>
> Sent: Friday, May 7, 2021 4:48 PM
> To: dev@dpdk.org
> Cc: Thierry Herbelot <thierry.herbelot@6wind.com>; thomas@monjalon.net;
> Juraj Linkeš <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; Ruifeng Wang
> <Ruifeng.Wang@arm.com>
> Subject: [PATCH-V7] config/arm: add Qualcomm Centriq 2400 SoC config
>
> From the documentation:
> "The SoC configuration is a combination of implementer and CPU part
> number configuration and SoC-specific configuration."
>
> Align Qualcomm SoC configuration with the configuration of other server
> SoCs (eMAG, Kunpeng 9x0): add a soc configuration to the existing
> implementer configuration, and a cross file.
>
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> --
> V7:
> - use a more specific subject
> - add a cross file
> V6:
> - rebase after merge of "doc: fix Arm SoCs list"
> V5:
> - rebase after
> http://patches.dpdk.org/project/dpdk/patch/20210429070751.6065-1-
> david.marchand@redhat.com/
> V4:
> - use a more specific SoC name
> V3:
> - include doc patch
> - remove Fixes line
> V2:
> - use the right original commit in Fixes
> ---
> config/arm/arm64_centriq2400_linux_gcc | 16 ++++++++++++++++
> config/arm/meson.build | 9 +++++++++
> 2 files changed, 25 insertions(+)
> create mode 100644 config/arm/arm64_centriq2400_linux_gcc
>
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2021-05-13 9:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 16:08 [dpdk-dev] [PATCH] config/arm: restore support for Qualcomm servers Thierry Herbelot
2021-04-28 17:47 ` Thomas Monjalon
2021-04-28 18:21 ` Honnappa Nagarahalli
2021-04-28 18:26 ` Thierry Herbelot
2021-04-29 7:09 ` David Marchand
2021-04-29 8:06 ` [dpdk-dev] [PATCH-V2] " Thierry Herbelot
2021-04-29 9:16 ` Juraj Linkeš
2021-04-29 9:23 ` [dpdk-dev] [PATCH-V3] " Thierry Herbelot
2021-04-29 10:00 ` Juraj Linkeš
2021-04-29 10:07 ` [dpdk-dev] [PATCH-V4] " Thierry Herbelot
2021-04-29 15:03 ` Ruifeng Wang
2021-04-29 15:16 ` [dpdk-dev] [PATCH-V5] " Thierry Herbelot
2021-04-30 6:07 ` Juraj Linkeš
2021-05-06 9:25 ` [dpdk-dev] [PATCH-V6] " Thierry Herbelot
2021-05-07 7:22 ` Ruifeng Wang
2021-05-07 7:43 ` Juraj Linkeš
2021-05-07 8:48 ` [dpdk-dev] [PATCH-V7] config/arm: add Qualcomm Centriq 2400 SoC config Thierry Herbelot
2021-05-13 9:35 ` Ruifeng Wang [this message]
2021-05-19 10:09 ` 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=AM5PR0802MB24653C60403775439739BAC09E519@AM5PR0802MB2465.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=thierry.herbelot@6wind.com \
--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).