From: Thomas Monjalon <thomas@monjalon.net>
To: Doug Foster <doug.foster@arm.com>
Cc: Wathsala Vithanage <wathsala.vithanage@arm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, nd@arm.com, Dhruv Tripathi <dhruv.tripathi@arm.com>
Subject: Re: [PATCH] config/arm: update neoverse n3 SoC and add neoverse V3
Date: Wed, 28 May 2025 18:41:08 +0200 [thread overview]
Message-ID: <7878089.DvuYhMxLoT@thomas> (raw)
In-Reply-To: <20250516161558.1482246-1-doug.foster@arm.com>
16/05/2025 18:15, Doug Foster:
> Arm Neoverse N3 build configuration is updated to include mcpu that
> aligns with latest GCC. Also, add Arm Neoverse V3 build configuration.
>
> Signed-off-by: Doug Foster <doug.foster@arm.com>
> Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> Reviewed-by: Dhruv Tripathi <dhruv.tripathi@arm.com>
Split in 2 patches and pushed, thanks.
prev parent reply other threads:[~2025-05-28 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 16:15 Doug Foster
2025-05-28 16:41 ` Thomas Monjalon [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=7878089.DvuYhMxLoT@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dhruv.tripathi@arm.com \
--cc=doug.foster@arm.com \
--cc=nd@arm.com \
--cc=wathsala.vithanage@arm.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).