From: Keith Owens <kaos@ocs.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [patch 2.6.11-rc5] Add target debug_kallsyms
Date: Tue, 15 Mar 2005 08:49:35 +1100 [thread overview]
Message-ID: <31391.1110836975@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 14 Mar 2005 22:43:41 BST." <20050314214341.GF17925@mars.ravnborg.org>
On Mon, 14 Mar 2005 22:43:41 +0100,
Sam Ravnborg <sam@ravnborg.org> wrote:
>On Sat, Feb 26, 2005 at 09:50:02PM +1100, Keith Owens wrote:
>> Make it easier to generate maps for debugging kallsyms problems.
>> debug_kallsyms is only a debugging target so no help or silent mode.
>>
>> Signed-off-by: Keith Owens <kaos@ocs.com.au>
>Applied to my kbuild tree.
>I will remove it when we stop see kallsyms reports.
Good luck! Most of the kallsyms reports are not really kallsyms bugs,
rather they are caused by the kallsyms checking picking up toolchain
problems.
prev parent reply other threads:[~2005-03-14 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 10:50 Keith Owens
2005-03-14 21:43 ` Sam Ravnborg
2005-03-14 21:49 ` Keith Owens [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=31391.1110836975@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome