From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Paulo Marques <pmarques@grupopie.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: -mm: please drop h8300 kallsyms patch
Date: Mon, 8 Sep 2008 15:45:59 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0809081521270.19968@blonde.site> (raw)
Please drop h8300-kallsyms-exclude-local-symbols.patch from mm for now.
I'm all in favour of its intent, cutting local .Lfoo symbols out of the
the symbol table. But at present it's cutting out all .symbols - which
is very unfriendly to powerpc, whose every function is a .symbol!
The undotted symbol being the descriptor that points to the function.
My 2.6.27-rc5 powerpc System.map doesn't actually contain any .Lsymbols,
but I expect someone else's does: I doubt excluding .Lsymbols is the
right answer, though it would be an improvement.
Maybe Paulo or Sam has a grasp on what the different architectures'
toolchains do, and can suggest the right patch.
Thanks,
Hugh
reply other threads:[~2008-09-08 14:47 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=Pine.LNX.4.64.0809081521270.19968@blonde.site \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=sam@ravnborg.org \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).