From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, david.marchand@redhat.com
Subject: Re: [PATCH v3 0/2] build: add backward compatibility for nested drivers
Date: Thu, 16 Oct 2025 22:02:36 +0200 [thread overview]
Message-ID: <10319547.2WqB4rESCP@thomas> (raw)
In-Reply-To: <20250929100528.18365-1-ktraynor@redhat.com>
29/09/2025 12:05, Kevin Traynor:
> Since Intel drivers moved from 'net/*' to 'net/intel/*' there are some
> changes required when enabling or disabling those drivers from the meson
> command line. e.g. 'net/ixgbe' no longer works and needs to be replaced
> by 'net/intel/ixgbe'
>
> These patches are to allow backwards compatibility for legacy driver names
> and wildcarding of nested drivers e.g. 'net/ixgbe' and 'net/*'
Applied with Cc stable@dpdk.org, thanks.
prev parent reply other threads:[~2025-10-16 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 11:07 [PATCH 1/2] build: add backward compatibility for nested drivers 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 ` [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
2025-09-29 10:05 ` [PATCH v3 " Kevin Traynor
2025-09-29 10:05 ` [PATCH v3 1/2] " Kevin Traynor
2025-09-29 10:05 ` [PATCH v3 2/2] build: add backward compatibility for wildcarding " Kevin Traynor
2025-10-16 20:02 ` 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=10319547.2WqB4rESCP@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.