From: David Howells <dhowells@redhat.com>
To: Jan Dittmer <jdi@l4x.org>
Cc: dhowells@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Working frv toolchain?
Date: Mon, 05 Nov 2007 16:04:26 +0000 [thread overview]
Message-ID: <27945.1194278666@redhat.com> (raw)
In-Reply-To: <472B9479.7040105@l4x.org>
Jan Dittmer <jdi@l4x.org> wrote:
> Hrm, that gets me further, but one of the final stages fail:
Can you try the attached patch?
David
---
[PATCH] FRV: Fix the extern declaration of kallsyms_num_syms
From: David Howells <dhowells@redhat.com>
Fix the extern declaration of kallsyms_num_syms to indicate that the symbol
does not reside in the small-data storage space, and so may not be accessed
relative to the small data base register.
Signed-off-by: David Howells <dhowells@redhat.com>
---
kernel/kallsyms.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
index 474219a..fa84b83 100644
--- a/kernel/kallsyms.c
+++ b/kernel/kallsyms.c
@@ -32,7 +32,8 @@
/* These will be re-linked against their real values during the second link stage */
extern const unsigned long kallsyms_addresses[] __attribute__((weak));
-extern const unsigned long kallsyms_num_syms __attribute__((weak));
+extern const unsigned long kallsyms_num_syms
+__nongpreldata __attribute__((weak));
extern const u8 kallsyms_names[] __attribute__((weak));
extern const u8 kallsyms_token_table[] __attribute__((weak));
next prev parent reply other threads:[~2007-11-05 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 10:26 Working frv toolchain? Jan Dittmer
2007-10-29 13:06 ` David Howells
2007-10-29 19:24 ` Jan Dittmer
2007-10-30 14:17 ` David Howells
2007-10-30 14:18 ` David Howells
2007-10-30 16:06 ` Jan Dittmer
2007-11-02 21:19 ` Jan Dittmer
2007-11-03 10:58 ` David Howells
2007-11-04 15:54 ` Jan Dittmer
2007-11-05 16:04 ` David Howells [this message]
2007-11-06 21:05 ` Jan Dittmer
2007-11-06 21:47 ` David Howells
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=27945.1194278666@redhat.com \
--to=dhowells@redhat.com \
--cc=jdi@l4x.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.