From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 0/4] remove common iavf and idpf drivers
Date: Thu, 30 Jan 2025 14:28:22 +0000 [thread overview]
Message-ID: <Z5uMhrTlWilioywA@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8xrWgQ8-hNJ0hA8CauEkCandBQNK+17JhueCx7WE_K_zQ@mail.gmail.com>
On Thu, Jan 30, 2025 at 02:55:54PM +0100, David Marchand wrote:
> Hello Bruce,
>
> On Thu, Jan 30, 2025 at 1:48 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > The iavf and idpf common directories were used only to share code
> > between multiple net drivers and did not need to be drivers in their own
> > right, since it is just as easy to have a dependency from one net driver
> > on another as a net driver on a common one.
> >
> > This patchset therefore aims to eliminate the two unnecessary common
> > drivers. It does so as follows:
> >
> > * merging common/idpf into net/idpf and updating the cpfl dependency to
> > point to the net driver.
> > * merging common/iavf into net/iavf and similarly updating the
> > dependencies, including the paths from idpf (which does not directly
> > depend on iavf, but does make use of the definitions in the iavf
> > header files).
> >
> > Separately, two other cleanups are done - one to remove an unnecessary
> > warning disable flag. The second is a little more complex - it makes the
> > dependency between ice and iavf an optional one, by having ice compile
> > in the necessary iavf shared code files in case iavf is disabled in the
> > build.
> >
> >
> > v2: include Release note updates
> >
> > Bruce Richardson (4):
> > drivers: merge common and net idpf drivers
> > net/idpf: re-enable unused variable warnings
> > drivers: move iavf common folder to iavf net
> > net/intel: allow building ice driver without iavf
>
> You'll probably need something like:
>
> $ git show --oneline 9863a695075109f15bbfa2f1a3042139f25d6493 --
> devtools/libabigail.abignore
> 9863a69507 net/liquidio: remove LiquidIO ethdev driver
> diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore
> index 585eb23c5e..03bfbce259 100644
> --- a/devtools/libabigail.abignore
> +++ b/devtools/libabigail.abignore
> @@ -25,6 +25,7 @@
> ;
> ; SKIP_LIBRARY=librte_common_mlx5_glue
> ; SKIP_LIBRARY=librte_net_mlx4_glue
> +; SKIP_LIBRARY=librte_net_liquidio
>
Yes, I see the libabigail errors in the CI now. V3 coming up...
/Bruce
next prev parent reply other threads:[~2025-01-30 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:36 [PATCH " Bruce Richardson
2025-01-28 16:36 ` [PATCH 1/4] drivers: merge common and net " Bruce Richardson
2025-01-28 16:36 ` [PATCH 2/4] net/idpf: re-enable unused variable warnings Bruce Richardson
2025-01-28 16:36 ` [PATCH 3/4] drivers: move iavf common folder to iavf net Bruce Richardson
2025-01-28 16:36 ` [PATCH 4/4] net/intel: allow building ice driver without iavf Bruce Richardson
2025-01-30 12:48 ` [PATCH v2 0/4] remove common iavf and idpf drivers Bruce Richardson
2025-01-30 12:48 ` [PATCH v2 1/4] drivers: merge common and net " Bruce Richardson
2025-01-30 12:48 ` [PATCH v2 2/4] net/idpf: re-enable unused variable warnings Bruce Richardson
2025-01-30 12:48 ` [PATCH v2 3/4] drivers: move iavf common folder to iavf net Bruce Richardson
2025-01-30 12:48 ` [PATCH v2 4/4] net/intel: allow building ice driver without iavf Bruce Richardson
2025-01-30 13:55 ` [PATCH v2 0/4] remove common iavf and idpf drivers David Marchand
2025-01-30 14:28 ` Bruce Richardson [this message]
2025-01-30 15:12 ` [PATCH v3 " Bruce Richardson
2025-01-30 15:12 ` [PATCH v3 1/4] drivers: merge common and net " Bruce Richardson
2025-01-30 15:12 ` [PATCH v3 2/4] net/idpf: re-enable unused variable warnings Bruce Richardson
2025-01-30 15:12 ` [PATCH v3 3/4] drivers: move iavf common folder to iavf net Bruce Richardson
2025-01-30 15:12 ` [PATCH v3 4/4] net/intel: allow building ice driver without iavf 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=Z5uMhrTlWilioywA@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).