From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: JBottomley@parallels.com, trivial@kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial next 7/9] scsi: Use vsprintf extention %pf with builtin_return_address
Date: Tue, 28 Feb 2012 16:07:32 -0500 (EST) [thread overview]
Message-ID: <20120228.160732.236576548660822884.davem@davemloft.net> (raw)
In-Reply-To: <aa5a8942edf8a59745a514a099e78eaaae03fe26.1330454853.git.joe@perches.com>
From: Joe Perches <joe@perches.com>
Date: Tue, 28 Feb 2012 10:49:36 -0800
> 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>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2012-02-28 21:07 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
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 [this message]
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=20120228.160732.236576548660822884.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=JBottomley@parallels.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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).