From: David Howells <dhowells@redhat.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Add initdata variable spec in a header file
Date: Tue, 04 Jan 2005 19:49:25 +0000 [thread overview]
Message-ID: <17767.1104868165@redhat.com> (raw)
The attached patch marks a variable as __initdata in a header file so that the
FRV gcc generates the correct access method as initdata variables are too far
from the GPREL pointer to access directly.
Signed-Off-By: David Howells <dhowells@redhat.com>
---
warthog>diffstat initdata-2610mm1.diff
bootmem.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -uNrp /warthog/kernels/linux-2.6.10-mm1/include/linux/bootmem.h linux-2.6.10-mm1-frv/include/linux/bootmem.h
--- /warthog/kernels/linux-2.6.10-mm1/include/linux/bootmem.h 2005-01-04 11:15:26.000000000 +0000
+++ linux-2.6.10-mm1-frv/include/linux/bootmem.h 2005-01-04 14:59:53.000000000 +0000
@@ -91,7 +91,7 @@ extern void *__init alloc_large_system_h
#else
#define HASHDIST_DEFAULT 0
#endif
-extern int hashdist; /* Distribute hashes across NUMA nodes? */
+extern int __initdata hashdist; /* Distribute hashes across NUMA nodes? */
#endif /* _LINUX_BOOTMEM_H */
reply other threads:[~2005-01-04 19:56 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=17767.1104868165@redhat.com \
--to=dhowells@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.