From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Naveen N Rao (AMD)" <naveen@kernel.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
x86@kernel.org
Subject: Re: [PATCH] Documentation/x86: Clarify naming of CPU features for /proc/cpuinfo
Date: Thu, 3 Apr 2025 17:55:35 +0700 [thread overview]
Message-ID: <Z-5pJ6iat-uptEh9@archie.me> (raw)
In-Reply-To: <20250403094308.2297617-1-naveen@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Thu, Apr 03, 2025 at 03:13:08PM +0530, Naveen N Rao (AMD) wrote:
> If the comment on the line for the #define X86_FEATURE_* starts with a
> -double-quote character (""), the string inside the double-quote characters
> -will be the name of the flags. For example, the flag "sse4_1" comes from
> -the comment "sse4_1" following the X86_FEATURE_XMM4_1 definition.
> +double-quote character (""), the string inside the double-quote characters will
"... the quoted string ..."
> +be the name of the flag. For example, the flag "sse4_1" comes from the comment
> +"sse4_1" following the X86_FEATURE_XMM4_1 definition. /proc/cpuinfo is a
> +userspace interface and must remain constant. If, for some reason, the naming
> +of X86_FEATURE_<name> changes, one shall retain the name already used in
> +/proc/cpuinfo.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-03 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 9:43 [PATCH] Documentation/x86: Clarify naming of CPU features for /proc/cpuinfo Naveen N Rao (AMD)
2025-04-03 10:55 ` Bagas Sanjaya [this message]
2025-04-03 12:17 ` Borislav Petkov
2025-04-03 13:10 ` Naveen N Rao
2025-04-03 13:21 ` Borislav Petkov
2025-04-03 15:02 ` Naveen N Rao
2025-04-09 11:13 ` [PATCH 1/2] Documentation/x86: Update the " Borislav Petkov
2025-04-09 12:04 ` [tip: x86/urgent] " tip-bot2 for Naveen N Rao (AMD)
2025-04-09 11:14 ` [PATCH 2/2] Documentation/x86: Zap the subsection letters Borislav Petkov
2025-04-09 12:04 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov (AMD)
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=Z-5pJ6iat-uptEh9@archie.me \
--to=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naveen@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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