From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 00/10] centralise base code handling for drivers
Date: Wed, 2 Apr 2025 15:08:45 +0200 [thread overview]
Message-ID: <CAJFAV8w3uth7PNR8e9gD0vOhmdd29TdaLtcT0mE2Y2D6eRV9Ag@mail.gmail.com> (raw)
In-Reply-To: <20250331161000.9886-1-bruce.richardson@intel.com>
On Mon, Mar 31, 2025 at 6:10 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> Many DPDK drivers use the same pattern for base code handling, having
> a meson.build file in the base code directory which optionally defines
> some custom cflags for the base code build, then builds the code as a
> static library and extracts the objects from it. (The reason behind this
> is that, in meson, cflags apply per-object, so we need to have a
> separate build object for the base code to use custom flags)
>
> This patchset deduplicates this logic by putting it into the
> drivers/meson.build file, and allowing individual drivers to then just
> specify values for "base_sources" and "base_cflags".
In general, this series lgtm.
> Depends-on: Series-34946 ("net/intel: clean up base code build")
This dependency is a bit problematic, as this series is already merged
in next-net-intel.
There will be some merge conflict to resolve.
Instead, it would have been better if next-net-intel relied on this new series.
After this series, the only remaining special case is for SVE stuff in
net/hns3 and we would have all source compiling handled by
drivers/meson.build.
Do you plan to clean it too?
--
David Marchand
next prev parent reply other threads:[~2025-04-02 13:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 16:09 Bruce Richardson
2025-03-31 16:09 ` [PATCH 01/10] build: add generic support for base code in drivers Bruce Richardson
2025-03-31 16:09 ` [PATCH 02/10] common/sfc_efx: use common base code build handling Bruce Richardson
2025-04-01 7:10 ` Andrew Rybchenko
2025-03-31 16:09 ` [PATCH 03/10] net/hinic: " Bruce Richardson
2025-03-31 16:09 ` [PATCH 04/10] net/intel: " Bruce Richardson
2025-04-02 13:05 ` David Marchand
2025-04-02 13:42 ` Bruce Richardson
2025-03-31 16:09 ` [PATCH 05/10] net/ngbe: " Bruce Richardson
2025-03-31 16:09 ` [PATCH 06/10] net/octeontx: " Bruce Richardson
2025-03-31 16:09 ` [PATCH 07/10] net/qede: " Bruce Richardson
2025-03-31 16:09 ` [PATCH 08/10] net/thunderx: " Bruce Richardson
2025-03-31 16:09 ` [PATCH 09/10] net/txgbe: " Bruce Richardson
2025-03-31 16:10 ` [PATCH 10/10] raw/ifpga: " Bruce Richardson
2025-04-01 0:27 ` Xu, Rosen
2025-04-02 13:08 ` David Marchand [this message]
2025-04-02 13:44 ` [PATCH 00/10] centralise base code handling for drivers 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=CAJFAV8w3uth7PNR8e9gD0vOhmdd29TdaLtcT0mE2Y2D6eRV9Ag@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).