From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] FRV: Fix the extern declaration of kallsyms_num_syms [try #2]
Date: Thu, 15 Nov 2007 22:55:37 +0000 [thread overview]
Message-ID: <16597.1195167337@redhat.com> (raw)
In-Reply-To: <20071115144007.08760570.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> hm, OK, so it lines up with what scripts/kallsyms.c presently does.
I'm sure there's a way to pass the kallsyms_num_syms value directly by way of
the linker rather than consigning it to a bit of memory.
The immediately obvious way is to declare it to be at an address that it the
symbol count value, and then C can do "&kallsyms_num_syms" to get at it.
Horrible, I know, but I'm not sure it's worse than some of the other stuff we
do.
David
prev parent reply other threads:[~2007-11-15 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 16:53 [PATCH] FRV: Fix the extern declaration of kallsyms_num_syms [try #2] David Howells
2007-11-15 22:40 ` Andrew Morton
2007-11-15 22:44 ` Andrew Morton
2007-11-15 22:55 ` David Howells [this message]
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=16597.1195167337@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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