public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	Anatoly Burakov <anatoly.burakov@intel.com>, <stable@dpdk.org>,
	Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [V2] drivers/net: reorder Intel drivers list in meson script
Date: Fri, 23 Jan 2026 16:50:29 +0000	[thread overview]
Message-ID: <aXOm1Xep0eINPO3y@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260123162707.1854505-1-thierry.herbelot@6wind.com>

On Fri, Jan 23, 2026 at 05:27:07PM +0100, Thierry Herbelot wrote:
> After an upstream patch (see Fixes), net_ixgbe_vf is no longer
> declared in testpmd PMD info, when compiling under Redhat-9:
> 
> > $ meson setup build && ninja -C build
> > $ ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd|grep ixgbe
> >     "name": "net_ixgbe",
> 
> Name 'net_ixgbe_vf' should also be reported.
> 
> One workaround is to move 'intel/ixgbe' as last in the list of Intel
> drivers. This restores net_ixgbe_vf under Redhat-9:
> 
> > $ meson setup build && ninja -C build
> > $ ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd|grep ixgbe
> >     "name": "net_ixgbe_vf",
> >     "name": "net_ixgbe",
> 
> Fixes: 04f1b16c54f3 ("drivers: merge common and net idpf drivers")
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> ---
> V2: use shorter lines in commit log.
> ---
>  drivers/net/meson.build | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/meson.build b/drivers/net/meson.build
> index c7dae4ad273c..8d96244cdbb0 100644
> --- a/drivers/net/meson.build
> +++ b/drivers/net/meson.build
> @@ -32,8 +32,8 @@ drivers = [
>          'intel/ice',
>          'intel/idpf',
>          'intel/ipn3ke',
> -        'intel/ixgbe',
>          'intel/cpfl',  # depends on idpf, so must come after it
> +        'intel/ixgbe',
>          'ionic',
>          'mana',
>          'memif',

This is a strange one - did you do any investgation into why or how this
fixes things? You describe it as a workaround so any hints towards a proper
root cause and fix are welcome :-)

  reply	other threads:[~2026-01-23 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 16:21 [PATCH] drivers/net: reorder Intel drivers list in meson script Thierry Herbelot
2026-01-23 16:27 ` [V2] " Thierry Herbelot
2026-01-23 16:50   ` Bruce Richardson [this message]
2026-01-23 16:57     ` Thierry Herbelot
2026-02-16 10:48       ` Bruce Richardson
2026-02-16 11:32         ` Bruce Richardson
2026-02-16 17:39           ` Thomas Monjalon
2026-02-17 12:48 ` [PATCH] usertools/pmdinfo: fix search for PMD info string Bruce Richardson
2026-02-17 17:53   ` David Marchand
2026-02-17 17:59     ` Bruce Richardson
2026-02-18  7:43       ` Thierry Herbelot
2026-02-18  8:38       ` David Marchand
2026-02-18  9:41   ` Robin Jarry
2026-03-17 13:57     ` Thomas Monjalon

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=aXOm1Xep0eINPO3y@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=stable@dpdk.org \
    --cc=thierry.herbelot@6wind.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