From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/8] remove non-base files from base folders
Date: Fri, 14 Aug 2026 16:37:43 +0100 [thread overview]
Message-ID: <20260814153755.940302-1-bruce.richardson@intel.com> (raw)
The base code folders for intel drivers contained the compatibility
*_osdep.h files as well as meson.build files, both of which are
editable via regular DPDK patches. Although the DPDK documentation
allows this arrangement, I (for one) have always found it a little
awkward and confusing to have editable and non-editable files mixed.
For Intel drivers only, this patchset moves osdep file out of base,
and merges the (in most cases trivial) meson.build files from base
into the main driver meson.build file.
After this patch we have a clean separation - any files in base,
with no exceptions, should be updated only via snapshot update
patchsets from Intel. All files outside base are normal DPDK files
that can be modified by any patch.
Bruce Richardson (8):
net/e1000: move editable files out of base folder
net/fm10k: move editable files out of base folder
net/i40e: move editable files out of base folder
net/iavf: move editable files out of base folder
net/ice: move editable files out of base folder
net/idpf: move editable files out of base folder
net/ixgbe: move editable files out of base folder
net/ice: consolidate the sources list
drivers/net/intel/cpfl/cpfl_actions.h | 2 +-
drivers/net/intel/cpfl/cpfl_controlq.h | 2 +-
drivers/net/intel/e1000/base/README | 9 ---
drivers/net/intel/e1000/base/meson.build | 24 -------
.../net/intel/e1000/{base => }/e1000_osdep.c | 0
.../net/intel/e1000/{base => }/e1000_osdep.h | 4 +-
drivers/net/intel/e1000/em_rxtx.c | 2 +-
drivers/net/intel/e1000/igc_ethdev.h | 2 +-
drivers/net/intel/e1000/meson.build | 22 ++++++-
drivers/net/intel/fm10k/base/meson.build | 11 ----
.../net/intel/fm10k/{base => }/fm10k_osdep.h | 4 +-
drivers/net/intel/fm10k/meson.build | 9 ++-
drivers/net/intel/i40e/base/README | 8 ---
drivers/net/intel/i40e/base/meson.build | 12 ----
.../net/intel/i40e/{base => }/i40e_osdep.h | 4 +-
drivers/net/intel/i40e/meson.build | 10 ++-
drivers/net/intel/iavf/base/README | 8 ---
.../iavf/{base/iavf_impl.c => iavf_osdep.c} | 0
.../net/intel/iavf/{base => }/iavf_osdep.h | 2 +
drivers/net/intel/iavf/meson.build | 2 +-
drivers/net/intel/ice/base/README | 8 ---
drivers/net/intel/ice/base/meson.build | 51 ---------------
drivers/net/intel/ice/{base => }/ice_osdep.h | 4 +-
drivers/net/intel/ice/meson.build | 62 ++++++++++++++++---
drivers/net/intel/idpf/base/README | 8 ---
drivers/net/intel/idpf/base/meson.build | 7 ---
.../net/intel/idpf/{base => }/idpf_osdep.h | 4 +-
drivers/net/intel/idpf/idpf_ptp.h | 2 +-
drivers/net/intel/idpf/meson.build | 5 +-
drivers/net/intel/ixgbe/base/README | 9 ---
drivers/net/intel/ixgbe/base/meson.build | 19 ------
drivers/net/intel/ixgbe/ixgbe_ethdev.c | 12 ++--
drivers/net/intel/ixgbe/ixgbe_flow.c | 12 ++--
.../net/intel/ixgbe/{base => }/ixgbe_osdep.h | 2 +
drivers/net/intel/ixgbe/meson.build | 17 ++++-
35 files changed, 148 insertions(+), 211 deletions(-)
delete mode 100644 drivers/net/intel/e1000/base/meson.build
rename drivers/net/intel/e1000/{base => }/e1000_osdep.c (100%)
rename drivers/net/intel/e1000/{base => }/e1000_osdep.h (98%)
delete mode 100644 drivers/net/intel/fm10k/base/meson.build
rename drivers/net/intel/fm10k/{base => }/fm10k_osdep.h (98%)
delete mode 100644 drivers/net/intel/i40e/base/meson.build
rename drivers/net/intel/i40e/{base => }/i40e_osdep.h (98%)
rename drivers/net/intel/iavf/{base/iavf_impl.c => iavf_osdep.c} (100%)
rename drivers/net/intel/iavf/{base => }/iavf_osdep.h (98%)
delete mode 100644 drivers/net/intel/ice/base/meson.build
rename drivers/net/intel/ice/{base => }/ice_osdep.h (99%)
delete mode 100644 drivers/net/intel/idpf/base/meson.build
rename drivers/net/intel/idpf/{base => }/idpf_osdep.h (99%)
delete mode 100644 drivers/net/intel/ixgbe/base/meson.build
rename drivers/net/intel/ixgbe/{base => }/ixgbe_osdep.h (99%)
--
2.53.0
next reply other threads:[~2026-08-14 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 15:37 Bruce Richardson [this message]
2026-08-14 15:37 ` [PATCH 1/8] net/e1000: move editable files out of base folder Bruce Richardson
2026-08-14 15:37 ` [PATCH 2/8] net/fm10k: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 3/8] net/i40e: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 4/8] net/iavf: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 5/8] net/ice: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 6/8] net/idpf: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 7/8] net/ixgbe: " Bruce Richardson
2026-08-14 15:37 ` [PATCH 8/8] net/ice: consolidate the sources list 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=20260814153755.940302-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.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