From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: RE: [PATCH] config/arm: fix march features not being set
Date: Tue, 11 Mar 2025 19:44:53 +0000 [thread overview]
Message-ID: <PAWPR08MB89090328B8F3D2F4FC653C429FD12@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <BY3PR18MB4785BC97AD137F9FFFACAABDC8D62@BY3PR18MB4785.namprd18.prod.outlook.com>
Hi Jerin,
We are looking into this internally.
Thanks.
> -----Original Message-----
> From: Jerin Jacob <jerinj@marvell.com>
> Sent: Monday, March 10, 2025 9:23 AM
> To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Wathsala
> Wathawana Vithanage <wathsala.vithanage@arm.com>; Bruce Richardson
> <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>;
> thomas@monjalon.net; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>
> Subject: RE: [PATCH] config/arm: fix march features not being set
>
> > -----Original Message-----
> > From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
> > Sent: Saturday, March 8, 2025 2:29 PM
> > To: Jerin Jacob <jerinj@marvell.com>; Wathsala Vithanage
> > <wathsala.vithanage@arm.com>; Bruce Richardson
> > <bruce.richardson@intel.com>
> > Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula
> > <pbhagavatula@marvell.com>
> > Subject: [PATCH] config/arm: fix march features not being set
> >
> > From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >
> > Fix extra_march_features not being added to mcpu flags when SoC
> > configuration advertises them.
> >
> > Fixes: c02c01dbf907 ("config/arm: prefer strict use of -mcpu if
> > supported")
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
>
> Wathsala, Could you review this patch so that it can be part of rc3. Following
> machines configs are broken
>
> [main]dell[dpdk.org] $ git grep -p extra_march_features
> config/arm/meson.build=soc_cn10k = {
> config/arm/meson.build: 'extra_march_features': ['crypto'],
> config/arm/meson.build=soc_grace = {
> config/arm/meson.build: 'extra_march_features': ['crypto'],
> config/arm/meson.build=soc_graviton3 = {
> config/arm/meson.build: 'extra_march_features': ['crypto'],
> config/arm/meson.build=soc_graviton4 = {
> config/arm/meson.build: 'extra_march_features': ['crypto'],
> config/arm/meson.build=soc_odyssey = {
> config/arm/meson.build: 'extra_march_features': ['crypto'],
next prev parent reply other threads:[~2025-03-11 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 8:59 pbhagavatula
2025-03-10 14:23 ` Jerin Jacob
2025-03-11 19:44 ` Wathsala Wathawana Vithanage [this message]
2025-03-12 19:46 ` Wathsala Wathawana Vithanage
2025-03-13 4:42 ` Pavan Nikhilesh Bhagavatula
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=PAWPR08MB89090328B8F3D2F4FC653C429FD12@PAWPR08MB8909.eurprd08.prod.outlook.com \
--to=wathsala.vithanage@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.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).