DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>
Cc: bruce.richardson@intel.com, david.marchand@redhat.com,
	Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH 1/2] build: add backward compatibility for nested drivers
Date: Mon, 22 Sep 2025 17:51:31 +0200	[thread overview]
Message-ID: <2842623.IobQ9Gjlxr@thomas> (raw)
In-Reply-To: <20250922110708.47879-1-ktraynor@redhat.com>

22/09/2025 13:07, Kevin Traynor:
> --- a/drivers/meson.build
> +++ b/drivers/meson.build
> -# add cmdline disabled drivers and meson disabled drivers together
> -disable_drivers += ',' + get_option('disable_drivers')
> +# map legacy driver names
> +driver_map = {
> +    'net/e1000': 'net/intel/e1000',
> +    'net/fm10k': 'net/intel/fm10k',
> +    'net/i40e': 'net/intel/i40e',
> +    'net/iavf': 'net/intel/iavf',
> +    'net/ice': 'net/intel/ice',
> +    'net/idpf': 'net/intel/idpf',
> +    'net/ipn3ke': 'net/intel/ipn3ke',
> +    'net/ixgbe': 'net/intel/ixgbe',
> +    'net/cpfl': 'net/intel/cpfl',
> +}

Should we build this list inside a file drivers/net/intel/meson.build ?
I'm not sure my idea is better...

> +
> +# add cmdline drivers
> +foreach driver_type : [['disable', get_option('disable_drivers')],
> +                       ['enable', get_option('enable_drivers')]]
> +    driver_list_name = driver_type[0] + '_drivers'
> +    cmdline_drivers = ',' + driver_type[1]
> +
> +    foreach driver : cmdline_drivers.split(',')
> +        if driver_map.has_key(driver)

I feel we need comments for above parsing.

> +            driver_mapped = driver_map[driver]
> +            warning('Driver name "@0@" is deprecated, please use "@1@" instead.'

Not sure about this warning.
We can keep compatibility without saying it is deprecated.

> +                    .format(driver, driver_mapped))
> +            driver = driver_mapped
> +        endif
> +        if driver_list_name == 'disable_drivers'
> +            disable_drivers += ',' + driver
> +        else
> +            enable_drivers += ',' + driver
> +        endif
> +    endforeach
> +endforeach
> +
> +# add cmdline drivers and meson drivers together

This comment is not clear.

>  disable_drivers = run_command(list_dir_globs, disable_drivers, check: true).stdout().split()
> -
> -# add cmdline enabled drivers and meson enabled drivers together
> -enable_drivers = ',' + get_option('enable_drivers')



  parent reply	other threads:[~2025-09-22 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 11:07 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
2025-09-22 15:51 ` Thomas Monjalon [this message]
2025-09-23 13:08   ` [PATCH 1/2] build: add backward compatibility for " 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=2842623.IobQ9Gjlxr@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.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).