From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"mkashani@nvidia.com" <mkashani@nvidia.com>,
"rasland@nvidia.com" <rasland@nvidia.com>, nd <nd@arm.com>,
Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Subject: Re: [PATCH] config/arm: update NVIDIA BlueField-3 configuration
Date: Wed, 19 Feb 2025 18:32:44 +0100 [thread overview]
Message-ID: <11075212.CDJkKcVGEf@thomas> (raw)
In-Reply-To: <PAWPR08MB8909905417281D380EEBEF0B9FC52@PAWPR08MB8909.eurprd08.prod.outlook.com>
19/02/2025 17:35, Wathsala Wathawana Vithanage:
> > Subject: [PATCH] config/arm: update NVIDIA BlueField-3 configuration
> >
> > ARM configuration requires explicit `mcpu` specifications in the implementor
> > description.
> >
> > The patch adds `mcpu` and `flags` description for the NVIDIA
> > BlueField-3 configuration.
> >
> > Signed-off-by: Gregory Etelson <getelson@nvidia.com>
>
> Acked-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
Adding error message:
"
The build was broken for BlueField-3:
ERROR: Problem encountered:
No suitable Arm mcpu name or custom mcpu definition object found.
"
and
Fixes: c02c01dbf907 ("config/arm: prefer strict use of -mcpu if supported")
Applied, thanks.
prev parent reply other threads:[~2025-02-19 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 14:04 [PATCH] testpmd: support meter_mark init_color in indirect list configuration Gregory Etelson
2025-02-17 16:24 ` Stephen Hemminger
2025-02-17 17:21 ` [PATCH v2] " Gregory Etelson
2025-02-19 18:39 ` Stephen Hemminger
2025-02-20 7:42 ` Ori Kam
2025-02-18 10:49 ` [PATCH] config/arm: update NVIDIA BlueField-3 configuration Gregory Etelson
2025-02-19 16:35 ` Wathsala Wathawana Vithanage
2025-02-19 17:32 ` 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=11075212.CDJkKcVGEf@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=nd@arm.com \
--cc=rasland@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.