From: tip-bot for Borislav Petkov <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, suravee.suthikulpanit@amd.com, tglx@linutronix.de,
mingo@kernel.org, bp@suse.de, linux-kernel@vger.kernel.org
Subject: [tip:x86/cpu] x86/CPU: Rename intel_cacheinfo.c to cacheinfo.c
Date: Sat, 12 May 2018 14:10:49 -0700 [thread overview]
Message-ID: <tip-1d200c078d0e3e49e2995b9d25fef8926d491f4f@git.kernel.org> (raw)
In-Reply-To: <1524864877-111962-4-git-send-email-suravee.suthikulpanit@amd.com>
Commit-ID: 1d200c078d0e3e49e2995b9d25fef8926d491f4f
Gitweb: https://git.kernel.org/tip/1d200c078d0e3e49e2995b9d25fef8926d491f4f
Author: Borislav Petkov <bp@suse.de>
AuthorDate: Fri, 27 Apr 2018 16:34:36 -0500
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Sun, 6 May 2018 12:49:15 +0200
x86/CPU: Rename intel_cacheinfo.c to cacheinfo.c
Since this file contains general cache-related information for x86,
rename the file to a more generic name.
Signed-off-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1524864877-111962-4-git-send-email-suravee.suthikulpanit@amd.com
---
arch/x86/kernel/cpu/Makefile | 2 +-
arch/x86/kernel/cpu/{intel_cacheinfo.c => cacheinfo.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile
index a66229f51b12..7a40196967cb 100644
--- a/arch/x86/kernel/cpu/Makefile
+++ b/arch/x86/kernel/cpu/Makefile
@@ -17,7 +17,7 @@ KCOV_INSTRUMENT_perf_event.o := n
nostackp := $(call cc-option, -fno-stack-protector)
CFLAGS_common.o := $(nostackp)
-obj-y := intel_cacheinfo.o scattered.o topology.o
+obj-y := cacheinfo.o scattered.o topology.o
obj-y += common.o
obj-y += rdrand.o
obj-y += match.o
diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c b/arch/x86/kernel/cpu/cacheinfo.c
similarity index 100%
rename from arch/x86/kernel/cpu/intel_cacheinfo.c
rename to arch/x86/kernel/cpu/cacheinfo.c
next prev parent reply other threads:[~2018-05-12 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 21:34 [PATCH v2 0/4] x86/CPU: Update AMD Last-Level-Cache Information Suravee Suthikulpanit
2018-04-27 21:34 ` [PATCH v2 1/4] x86/CPU/AMD: Remove unnecessary check for CONFIG_SMP Suravee Suthikulpanit
2018-05-12 21:09 ` [tip:x86/cpu] x86/CPU/AMD: Have smp_num_siblings and cpu_llc_id always be present tip-bot for Borislav Petkov
2018-04-27 21:34 ` [PATCH v2 2/4] perf/x86/amd/uncore: Fix amd_uncore_llc ID to use pre-defined cpu_llc_id Suravee Suthikulpanit
2018-05-12 21:10 ` [tip:x86/cpu] perf/events/amd/uncore: " tip-bot for Suravee Suthikulpanit
2018-04-27 21:34 ` [PATCH v2 3/4] x86/CPU: Rename intel_cacheinfo.c to cacheinfo.c Suravee Suthikulpanit
2018-05-12 21:10 ` tip-bot for Borislav Petkov [this message]
2018-04-27 21:34 ` [PATCH v2 4/4] x86/CPU/AMD: Calculate LLC ID from number of sharing threads Suravee Suthikulpanit
2018-05-12 21:11 ` [tip:x86/cpu] x86/CPU/AMD: Calculate last level cache " tip-bot for Suravee Suthikulpanit
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=tip-1d200c078d0e3e49e2995b9d25fef8926d491f4f@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
/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