From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"John Ogness" <john.ogness@linutronix.de>,
"Derek Barbosa" <debarbos@redhat.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@amutable.com>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Luca Boccassi" <luca.boccassi@gmail.com>,
linux-rt-devel@lists.linux.dev, debian-kernel@lists.debian.org,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Ahmed S. Darwish" <darwi@linutronix.de>
Subject: [PATCH v1 01/10] kconfig-checker: Add schema for rule files
Date: Fri, 6 Nov 2026 10:19:13 +0100 [thread overview]
Message-ID: <20261106091922.7560-2-darwi@linutronix.de> (raw)
In-Reply-To: <20261106091922.7560-1-darwi@linutronix.de>
The kconfig-checker YAML rule files describes which kernel .config symbols
are expected to be enabled or disabled. Introduce a schema for such files.
Describe and add rational for each element in the schema as well.
Signed-off-by: Ahmed S. Darwish <darwi@linutronix.de>
---
tools/kconfig-checker/schema.yml | 115 +++++++++++++++++++++++++++++++
1 file changed, 115 insertions(+)
create mode 100644 tools/kconfig-checker/schema.yml
diff --git a/tools/kconfig-checker/schema.yml b/tools/kconfig-checker/schema.yml
new file mode 100644
index 000000000000..a7f1b0a78cc7
--- /dev/null
+++ b/tools/kconfig-checker/schema.yml
@@ -0,0 +1,115 @@
+# SPDX-License-Identifier: GPL-2.0-only
+
+"$schema": "https://json-schema.org/draft-07/schema"
+
+title: Schema for kconfig-checker rule files
+type: object
+required: [rules]
+additionalProperties: false
+
+properties:
+ #
+ # Optional base URL for the documentation page used by rationale
+ # links. See `docs_hint`.
+ #
+ docs_url:
+ type: string
+ format: uri
+
+ rules:
+ type: array
+ minItems: 1
+ items:
+ type: object
+ oneOf:
+ - required: [name]
+ - required: [name_pattern]
+ required: [expected, severity]
+ additionalProperties: false
+
+ properties:
+ #
+ # Exact kernel configuration symbol to check.
+ #
+ # Example: CONFIG_PREEMPT_RT
+ #
+ name:
+ type: string
+ pattern: '^CONFIG_[A-Z0-9_]+$'
+
+ #
+ # Regex matching one or more kernel configuration symbols.
+ #
+ # Example: CONFIG_DEBUG_.*
+ #
+ name_pattern:
+ type: string
+ format: regex
+
+ #
+ # Expected value for the matching kernel configuration option.
+ #
+ # Values:
+ #
+ # y option is expected to be enabled (built-in or module).
+ # n option is expected to be disabled or unset.
+ # allowed option is permitted and must not be reported as a violation.
+ # This is used to exempt a specific symbol from a broader
+ # `name_pattern` rule with `expected: n`.
+ #
+ expected:
+ type: string
+ enum: [y, n, allowed]
+
+ #
+ # Issue severity to report when the configuration rule is not met.
+ #
+ # Higher severities should be reserved for rules affecting correctness.
+ #
+ severity:
+ type: string
+ enum: [fatal, high, medium, low, info]
+
+ #
+ # Optional documentation anchor for this rule.
+ #
+ # The rationale URL is built from `docs_url` plus an HTML fragment
+ # identifier.
+ #
+ # If `docs_hint` is set to `config`, then the HTML fragment id is
+ # derived from the kernel configuration symbol name:
+ #
+ # CONFIG_DRM -> #config-drm
+ #
+ # For example, with below docs_url:
+ #
+ # https://docs.kernel.org/core-api/real-time/kernel-configuration.html
+ #
+ # and the symbol entry:
+ #
+ # - name: CONFIG_DRM
+ # expected: n
+ # severity: info
+ # docs_hint: config
+ #
+ # the rationale URL becomes:
+ #
+ # https://docs.kernel.org/core-api/real-time/kernel-configuration.html#config-drm
+ #
+ # If `docs_hint` is any other string, that string is used directly as
+ # the HTML fragment identifier.
+ #
+ docs_hint:
+ type: string
+ anyOf:
+ - const: config
+ - pattern: '^\S+$' # URI fragments cannot have spaces
+
+ #
+ # Optional human-readable explanation for the rule.
+ #
+ # This text should explain why the option is expected to have the given
+ # value, and may span multiple lines.
+ #
+ rationale:
+ type: string
--
2.56.0
next prev parent reply other threads:[~2026-11-06 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:19 [PATCH v1 00/10] tools: Introduce a kernel configuration checker Ahmed S. Darwish
2026-11-06 9:19 ` Ahmed S. Darwish [this message]
2026-11-06 9:19 ` [PATCH v1 02/10] kconfig-checker: Introduce PREEMPT_RT configuration rules Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 03/10] kconfig-checker: Add the configuration checker code Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 04/10] kconfig: Introduce checkconfig target Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 05/10] Documentation: Describe kconfig-checker usage and design Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 06/10] kconfig-checker: Split schema to support component reuse Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 07/10] kconfig-checker: Introduce overlays schema Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 08/10] kconfig-checker: Add support for rule overlays Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 09/10] Documentation: Describe kconfig-checker overlays Ahmed S. Darwish
2026-11-06 9:19 ` [PATCH v1 10/10] kconfig: Introduce OVERLAY= for make checkconfig Ahmed S. Darwish
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=20261106091922.7560-2-darwi@linutronix.de \
--to=darwi@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=daan.j.demeyer@gmail.com \
--cc=debarbos@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=luca.boccassi@gmail.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zbyszek@amutable.com \
/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®