From: Michal Simek <monstr@monstr.eu>
To: Joe Perches <joe@perches.com>
Cc: Jiri Kosina <trivial@kernel.org>,
microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial next 4/9] microblaze: Use vsprintf extention %pf with builtin_return_address
Date: Tue, 13 Mar 2012 09:24:22 +0100 [thread overview]
Message-ID: <4F5F0436.4010106@monstr.eu> (raw)
In-Reply-To: <a980a9c855113fd613ee768a503f5bd5299efafd.1330454853.git.joe@perches.com>
Joe Perches wrote:
> Emit the function name not the address when possible.
>
> builtin_return_address() gives an address. When building
> a kernel with CONFIG_KALLSYMS, emit the actual function
> name not the address.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> arch/microblaze/mm/pgtable.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-03-13 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:49 [PATCH trivial next 0/9] treewide: Use vsprintf extention %pf Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 1/9] sparc: Use vsprintf extention %pf with builtin_return_address Joe Perches
2012-02-28 21:08 ` David Miller
2012-02-28 18:49 ` [PATCH trivial next 2/9] alpha: " Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 3/9] arm: " Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 4/9] microblaze: " Joe Perches
2012-03-13 8:24 ` Michal Simek [this message]
2012-02-28 18:49 ` [PATCH trivial next 5/9] powerpc: " Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 6/9] parisc: " Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 7/9] scsi: " Joe Perches
2012-02-28 21:07 ` David Miller
2012-02-28 18:49 ` [PATCH trivial next 8/9] staging: ramster: " Joe Perches
2012-02-28 18:49 ` [PATCH trivial next 9/9] gadget: " Joe Perches
2012-02-28 19:39 ` Felipe Balbi
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=4F5F0436.4010106@monstr.eu \
--to=monstr@monstr.eu \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=trivial@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 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).