From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>
Subject: [RFC] net/cnxk: only build if platform is specified
Date: Tue, 24 Feb 2026 12:37:09 -0800 [thread overview]
Message-ID: <20260224203709.27696-1-stephen@networkplumber.org> (raw)
The generic build was building for all SOC types and that
takes a long time (like 10 minutes). The driver should only be
built if soc_type is set to one of the know values.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/net/cnxk/meson.build | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/cnxk/meson.build b/drivers/net/cnxk/meson.build
index 53caa6c171..4a2f4e1a92 100644
--- a/drivers/net/cnxk/meson.build
+++ b/drivers/net/cnxk/meson.build
@@ -14,8 +14,10 @@ else
soc_type = platform
endif
-if soc_type != 'cn9k' and soc_type != 'cn10k' and soc_type != 'cn20k'
- soc_type = 'all'
+if soc_type != 'cn9k' and soc_type != 'cn10k' and soc_type != 'cn20k' and soc_type != 'all'
+ build = false
+ reason = 'not supported on soc_type ' + soc_type
+ subdir_done()
endif
sources = files(
--
2.51.0
next reply other threads:[~2026-02-24 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 20:37 Stephen Hemminger [this message]
2026-02-25 8:01 ` [EXTERNAL] [RFC] net/cnxk: only build if platform is specified Pavan Nikhilesh Bhagavatula
2026-02-25 17:43 ` Stephen Hemminger
2026-02-25 19:30 ` Pavan Nikhilesh Bhagavatula
2026-02-25 22:20 ` Stephen Hemminger
2026-02-26 4:50 ` Pavan Nikhilesh Bhagavatula
2026-02-26 21:16 ` Stephen Hemminger
2026-02-27 13:03 ` 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=20260224203709.27696-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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