From: Tony Luck <tony.luck@intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>, Rui Zhang <rui.zhang@intel.com>
Subject: [PATCH] x86/cpu: Drop spurious underscore from RAPTOR_LAKE #define
Date: Fri, 19 Nov 2021 09:08:32 -0800 [thread overview]
Message-ID: <20211119170832.1034220-1-tony.luck@intel.com> (raw)
Convention for all the other "lake" CPUs is all one word.
So s/RAPTOR_LAKE/RAPTORLAKE/
Reported-by: Rui Zhang <rui.zhang@intel.com>
Fixes: fbdb5e8f2926 ("x86/cpu: Add Raptor Lake to Intel family")
Signed-off-by: Tony Luck <tony.luck@intel.com>
---
Dave Hansen had thanked me for sending a simple patch on his first full
day as x86 maintainer. I had foolishly said: "You can hand me a giant
brown paper bag if I broke the build with that patch." Well, I didn't
break the build. But the one-line change had an error in every line. My
usual collection of brown bags is at the office. So I'll have to make
a new one. Then explain to my family the tradition of brown paper bags.
Big thanks to Rui for catching this before I'd have the extra shame
of needing to backport to stable.
---
arch/x86/include/asm/intel-family.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h
index 5a0bcf8b78d7..048b6d5aff50 100644
--- a/arch/x86/include/asm/intel-family.h
+++ b/arch/x86/include/asm/intel-family.h
@@ -108,7 +108,7 @@
#define INTEL_FAM6_ALDERLAKE 0x97 /* Golden Cove / Gracemont */
#define INTEL_FAM6_ALDERLAKE_L 0x9A /* Golden Cove / Gracemont */
-#define INTEL_FAM6_RAPTOR_LAKE 0xB7
+#define INTEL_FAM6_RAPTORLAKE 0xB7
/* "Small Core" Processors (Atom) */
--
2.31.1
next reply other threads:[~2021-11-19 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 17:08 Tony Luck [this message]
2021-11-30 22:11 ` [tip: x86/urgent] " tip-bot2 for Tony Luck
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=20211119170832.1034220-1-tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--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
all inboxes | Powered by JetHome®