From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH RFC 10/10] [RFC BOILERPLATE] scripts/get_abi.py: add support for undefined ABIs
Date: Fri, 17 Jan 2025 18:59:39 +0100 [thread overview]
Message-ID: <89e3c065815db72901294bdda8ca7f05ab86b881.1737135484.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1737135484.git.mchehab+huawei@kernel.org>
For this RFC, let's keep here a boilerplate, just as a reminder.
This patch contains just an skeleton for the argparse stuff. The plan
is to implement such functionality here to be able to fully replace
all get_abi.pl functionality.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
scripts/get_abi.py | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/scripts/get_abi.py b/scripts/get_abi.py
index 6a461f7cef32..221338c0d893 100755
--- a/scripts/get_abi.py
+++ b/scripts/get_abi.py
@@ -618,6 +618,27 @@ class AbiSearch:
args.parser.search_symbols(args.expression)
+class AbiUndefined:
+ """
+ Initialize an argparse subparser for logic to check undefined ABI at
+ the current machine's sysfs
+ """
+
+ def __init__(self, subparsers):
+ """Initialize argparse subparsers"""
+
+ parser = subparsers.add_parser("undefined",
+ formatter_class=argparse.ArgumentDefaultsHelpFormatter,
+ description="check undefined ABIs on local machine")
+
+ parser.set_defaults(func=self.run)
+
+ def run(self, args):
+ """Run subparser"""
+
+ args.parser.parse_abi()
+
+
def main():
"""Main program"""
@@ -633,6 +654,7 @@ def main():
AbiRest(subparsers)
AbiValidate(subparsers)
AbiSearch(subparsers)
+ AbiUndefined(subparsers)
args = parser.parse_args()
--
2.47.1
next prev parent reply other threads:[~2025-01-17 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 17:59 [PATCH RFC 00/10] Improve ABI documentation generation Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 01/10] scripts/get_abi.pl use label to better sort ABI symbols and files Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 02/10] ABI: sysfs-class-rfkill: fix kernelversion tags Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 03/10] ABI: sysfs-bus-coresight-*: " Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 04/10] ABI: sysfs-driver-dma-idxd: fix date tags Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 05/10] ABI: sysfs-fs-f2fs: " Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 06/10] ABI: sysfs-power: fix a what tag Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 07/10] [RFC] scripts: add a get_abi.py tool to generate ReST output Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 08/10] [RFC] scripts/get_abi.py: add support for symbol search Mauro Carvalho Chehab
2025-01-17 17:59 ` [PATCH RFC 09/10] [RFC] docs: use get_abi.py for ABI generation Mauro Carvalho Chehab
2025-01-17 17:59 ` Mauro Carvalho Chehab [this message]
2025-03-27 21:58 ` [f2fs-dev] [PATCH RFC 00/10] Improve ABI documentation generation patchwork-bot+f2fs
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=89e3c065815db72901294bdda8ca7f05ab86b881.1737135484.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®