From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
david.marchand@redhat.com, ferruh.yigit@xilinx.com,
mdr@ashroe.eu
Subject: [PATCH 1/1] devtools: eol abi as a separate function
Date: Mon, 8 Aug 2022 10:58:34 +0000 [thread overview]
Message-ID: <20220808105834.2826-2-mdr@ashroe.eu> (raw)
In-Reply-To: <20220808105834.2826-1-mdr@ashroe.eu>
Developer tools associated with abi are maintained with as part of
developer tooling, eal abi headers are maintained with eal, abi build
scripts are maintained with the build system and abi policy and version
documents along with rest of the documentation.
Major change is that individual components maintainers become
responsible for ensuring correctness of their map file(s).
Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
---
MAINTAINERS | 27 +++++++++------------------
1 file changed, 9 insertions(+), 18 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32ffdd1a61..25be8e35bc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -79,20 +79,27 @@ Developers and Maintainers Tools
M: Thomas Monjalon <thomas@monjalon.net>
F: MAINTAINERS
F: devtools/build-dict.sh
+F: devtools/check-abi.sh
+F: devtools/check-abi-version.sh
F: devtools/check-doc-vs-code.sh
F: devtools/check-dup-includes.sh
F: devtools/check-maintainers.sh
F: devtools/check-forbidden-tokens.awk
F: devtools/check-git-log.sh
F: devtools/check-spdx-tag.sh
+F: devtools/check-symbol-change.sh
F: devtools/check-symbol-maps.sh
F: devtools/checkpatches.sh
+F: devtools/gen-abi.sh
F: devtools/get-maintainer.sh
F: devtools/git-log-fixes.sh
F: devtools/load-devel-config
F: devtools/parse-flow-support.sh
F: devtools/process-iwyu.py
+F: devtools/update-abi.sh
F: devtools/update-patches.py
+F: devtools/update_version_map_abi.py
+F: devtools/libabigail.abignore
F: devtools/words-case.txt
F: license/
F: .editorconfig
@@ -103,11 +110,13 @@ F: Makefile
F: meson.build
F: meson_options.txt
F: config/
+F: buildtools/check-symbols.sh
F: buildtools/chkincs/
F: buildtools/call-sphinx-build.py
F: buildtools/get-cpu-count.py
F: buildtools/get-numa-count.py
F: buildtools/list-dir-globs.py
+F: buildtools/map-list-symbol.sh
F: buildtools/pkg-config/
F: buildtools/symlink-drivers-solibs.sh
F: buildtools/symlink-drivers-solibs.py
@@ -121,24 +130,6 @@ F: .travis.yml
F: .github/workflows/build.yml
F: .ci/
-ABI Policy & Versioning
-M: Ray Kinsella <mdr@ashroe.eu>
-F: lib/eal/include/rte_compat.h
-F: lib/eal/include/rte_function_versioning.h
-F: doc/guides/contributing/abi_*.rst
-F: doc/guides/rel_notes/deprecation.rst
-F: devtools/check-abi.sh
-F: devtools/check-abi-version.sh
-F: devtools/check-symbol-change.sh
-F: devtools/gen-abi.sh
-F: devtools/libabigail.abignore
-F: devtools/update-abi.sh
-F: devtools/update_version_map_abi.py
-F: buildtools/check-symbols.sh
-F: buildtools/map-list-symbol.sh
-F: drivers/*/*/*.map
-F: lib/*/*.map
-
Driver information
M: Neil Horman <nhorman@tuxdriver.com>
M: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
--
2.20.1
next prev parent reply other threads:[~2022-08-08 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 10:58 [PATCH 0/1] update abi maintainership Ray Kinsella
2022-08-08 10:58 ` Ray Kinsella [this message]
2022-10-11 0:36 ` [PATCH 1/1] devtools: eol abi as a separate function 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=20220808105834.2826-2-mdr@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.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;
as well as URLs for NNTP newsgroup(s).