From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: bruce.richardson@intel.com, david.marchand@redhat.com
Subject: Re: [PATCH 2/2] build: add backwards compatibility for wildcarding nested drivers
Date: Tue, 23 Sep 2025 14:09:18 +0100 [thread overview]
Message-ID: <3e90d7b4-ed82-4c9b-81bb-9dbf069ca39a@redhat.com> (raw)
In-Reply-To: <8866794.lvqk35OSZv@thomas>
On 22/09/2025 16:52, Thomas Monjalon wrote:
> 22/09/2025 13:07, Kevin Traynor:
>> Up until DPDK 25.03 'net/*' could be used with meson options
>> enable_drivers or disable_drivers to explicitly enable or
>> disable all net drivers.
>>
>> In DPDK 25.03 commit
>> c1d145834f28 ("net/intel: move Intel drivers to a subdirectory")
>> moved Intel drivers to 'net/intel/*' and 'net/*' no longer enabled
>> or disabled the Intel drivers.
>>
>> Expand wildcards handling to include nested drivers.
>> e.g. 'net/*' will also enable/disable drivers in 'net/*/*'
>>
>> This adds backwards compatibility so that so that 'net/*' will
>> continue to enable/disable Intel and any future nested drivers.
>>
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>> ---
>> drivers/meson.build | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/meson.build b/drivers/meson.build
>> index 3fbf04e1cd..ccd25e4d18 100644
>> --- a/drivers/meson.build
>> +++ b/drivers/meson.build
>> @@ -58,4 +58,9 @@ foreach driver_type : [['disable', get_option('disable_drivers')],
>> .format(driver, driver_mapped))
>> driver = driver_mapped
>> + elif driver.contains('*')
>> + if driver.endswith('/*') and not driver.contains('/*/*')
>> + # for wildcard add nested wildcard
>> + driver = driver + ',' + driver + '/*'
>> + endif
>
> The special pattern ** does not work in Meson?
>
>
I will check, thanks.
next prev parent reply other threads:[~2025-09-23 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 11:07 [PATCH 1/2] build: add backward compatibility for " Kevin Traynor
2025-09-22 11:07 ` [PATCH 2/2] build: add backwards compatibility for wildcarding " Kevin Traynor
2025-09-22 15:52 ` Thomas Monjalon
2025-09-23 13:09 ` Kevin Traynor [this message]
2025-09-22 15:51 ` [PATCH 1/2] build: add backward compatibility for " Thomas Monjalon
2025-09-23 13:08 ` Kevin Traynor
2025-09-23 13:28 ` Bruce Richardson
2025-09-24 8:43 ` Thomas Monjalon
2025-09-24 12:34 ` [PATCH v2 0/2] " Kevin Traynor
2025-09-24 12:34 ` [PATCH v2 1/2] " Kevin Traynor
2025-09-24 12:34 ` [PATCH v2 2/2] build: add backward compatibility for wildcarding " Kevin Traynor
2025-09-24 13:06 ` [PATCH v2 0/2] build: add backward compatibility for " Bruce Richardson
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=3e90d7b4-ed82-4c9b-81bb-9dbf069ca39a@redhat.com \
--to=ktraynor@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).