From: alison.schofield@intel.com
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: Alison Schofield <alison.schofield@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: [PATCH] docs: ABI: make the KernelVersion field optional
Date: Wed, 25 Jun 2025 19:40:58 -0700 [thread overview]
Message-ID: <20250626024101.792073-1-alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
The KernelVersion field has limited practical value. Git history
provides more accurate tracking of when features were introduced
and target kernel versions often change during development and
merge.
Label it optional.
Signed-off-by: Alison Schofield <alison.schofield@intel.com>
---
Plan B is to remove the field entirely.
Documentation/ABI/README | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/ABI/README b/Documentation/ABI/README
index ef0e6d11e919..315fffe1f831 100644
--- a/Documentation/ABI/README
+++ b/Documentation/ABI/README
@@ -46,7 +46,9 @@ Every file in these directories will contain the following information:
What: Short description of the interface
Date: Date created
-KernelVersion: Kernel version this feature first showed up in.
+KernelVersion: (Optional) Kernel version this feature first showed up in.
+ Note: git history often provides more accurate version
+ info, so this field may be omitted.
Contact: Primary contact for this interface (may be a mailing list)
Description: Long description of the interface and how to use it.
Users: All users of this interface who wish to be notified when
--
2.37.3
next reply other threads:[~2025-06-26 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 2:40 alison.schofield [this message]
2025-06-26 2:52 ` [PATCH] docs: ABI: make the KernelVersion field optional Randy Dunlap
2025-06-26 3:32 ` Alison Schofield
2025-06-26 3:53 ` Randy Dunlap
2025-06-26 3:10 ` dan.j.williams
2025-07-01 19:18 ` Jonathan Corbet
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=20250626024101.792073-1-alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=linux-doc@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