From: Arjan van de Ven <arjan@linux.intel.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, anton@samba.org
Subject: Re: [PATCH] bootgraph: fix for use with dot symbols
Date: Tue, 27 Jan 2009 20:53:59 -0800 [thread overview]
Message-ID: <497FE4E7.8070303@linux.intel.com> (raw)
In-Reply-To: <19599.1233113450@neuling.org>
Michael Neuling wrote:
> powerpc has dot symbols, so the dmesg output looks like:
>
> <4>[ 0.327310] calling .migration_init+0x0/0x9c @ 1
> <4>[ 0.327595] initcall .migration_init+0x0/0x9c returned 1 after 0 usecs
>
> The below fixes bootgraph.pl so it handles this correctly.
question for the ppc folks.... why does the "print symbol" magic format string
thing print a dot symbol and not the real function name?
Should that be fixed instead?
WARNING: multiple messages have this Message-ID (diff)
From: Arjan van de Ven <arjan@linux.intel.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, anton@samba.org
Subject: Re: [PATCH] bootgraph: fix for use with dot symbols
Date: Tue, 27 Jan 2009 20:53:59 -0800 [thread overview]
Message-ID: <497FE4E7.8070303@linux.intel.com> (raw)
In-Reply-To: <19599.1233113450@neuling.org>
Michael Neuling wrote:
> powerpc has dot symbols, so the dmesg output looks like:
>
> <4>[ 0.327310] calling .migration_init+0x0/0x9c @ 1
> <4>[ 0.327595] initcall .migration_init+0x0/0x9c returned 1 after 0 usecs
>
> The below fixes bootgraph.pl so it handles this correctly.
question for the ppc folks.... why does the "print symbol" magic format string
thing print a dot symbol and not the real function name?
Should that be fixed instead?
next prev parent reply other threads:[~2009-01-28 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 3:30 [PATCH] bootgraph: fix for use with dot symbols Michael Neuling
2009-01-28 3:30 ` Michael Neuling
2009-01-28 4:53 ` Arjan van de Ven [this message]
2009-01-28 4:53 ` Arjan van de Ven
2009-01-28 10:56 ` Anton Blanchard
2009-01-28 10:56 ` Anton Blanchard
2009-02-08 0:57 ` Michael Neuling
2009-02-08 0:57 ` Michael Neuling
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=497FE4E7.8070303@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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.