DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"mkashani@nvidia.com" <mkashani@nvidia.com>,
	"rasland@nvidia.com" <rasland@nvidia.com>,
	Wathsala Vithanage <wathsala.vithanage@arm.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Jerin Jacob <jerinj@marvell.com>
Subject: Re: [EXTERNAL] [PATCH] config/arm: fix meson for native instruction set Arm CPUs
Date: Wed, 19 Mar 2025 12:48:22 +0100	[thread overview]
Message-ID: <18752085.0ZKypZ73Fx@thomas> (raw)
In-Reply-To: <PH0PR18MB4086C3FC869C820807A4FA67DED92@PH0PR18MB4086.namprd18.prod.outlook.com>

19/03/2025 12:10, Pavan Nikhilesh Bhagavatula:
> > Hi Gregory,
> > 
> > > Arm meson.build unconditionally relays on the `extra_features`
> > > member of SoC configuration.
> > >
> > > SoC dictionary is populated for Arm CPUs with generic instruction set
> > > only.
> > > For Arm CPUs with native CPU instruction set the SoC dictionary is
> > > empty.
> > >
> > > meson setup failed for the BlueField-3 because it belongs to
> > > the native Arm CPU instruction set.
> > >
> > > The patch adds global definition for extra_features.
> > >
> > > Fixes: 7829776d0abf ("config/arm: add extra -march features")
> > > Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> 
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Applied, thanks.



      reply	other threads:[~2025-03-19 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 10:25 Gregory Etelson
2025-03-19 11:02 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-03-19 11:10   ` Pavan Nikhilesh Bhagavatula
2025-03-19 11:48     ` 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=18752085.0ZKypZ73Fx@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=jerinj@marvell.com \
    --cc=mkashani@nvidia.com \
    --cc=pbhagavatula@marvell.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 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).