From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: [PATCH] i386: init_intel_cacheinfo() can be __init
Date: Sat, 15 Jan 2005 21:27:12 -0800 [thread overview]
Message-ID: <41E9FB30.9060200@osdl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Correct .text references to .init.data; init_intel_cacheinfo()
can be __init.
These are references to:
static struct _cache_table cache_table[] __initdata = ...;
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to
0000008f R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to
0000009e R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to
000000a8 R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to
00000108 R_386_32 .init.data
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
arch/i386/kernel/cpu/intel_cacheinfo.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
---
[-- Attachment #2: intel_cache_sections.patch --]
[-- Type: text/x-patch, Size: 1318 bytes --]
Correct .text references to .init.data; init_intel_cacheinfo()
can be __init.
These are references to:
static struct _cache_table cache_table[] __initdata = ...;
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to 0000008f R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to 0000009e R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to 000000a8 R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/intel_cacheinfo.o .text refers to 00000108 R_386_32 .init.data
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
arch/i386/kernel/cpu/intel_cacheinfo.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naurp ./arch/i386/kernel/cpu/intel_cacheinfo.c~intel_cache_sections ./arch/i386/kernel/cpu/intel_cacheinfo.c
--- ./arch/i386/kernel/cpu/intel_cacheinfo.c~intel_cache_sections 2004-12-24 13:35:23.000000000 -0800
+++ ./arch/i386/kernel/cpu/intel_cacheinfo.c 2005-01-07 14:51:03.000000000 -0800
@@ -58,7 +58,7 @@ static struct _cache_table cache_table[]
{ 0x00, 0, 0}
};
-unsigned int init_intel_cacheinfo(struct cpuinfo_x86 *c)
+unsigned int __init init_intel_cacheinfo(struct cpuinfo_x86 *c)
{
unsigned int trace = 0, l1i = 0, l1d = 0, l2 = 0, l3 = 0; /* Cache sizes */
reply other threads:[~2005-01-16 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41E9FB30.9060200@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@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