mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "James E.J. Bottomley" <JBottomley@parallels.com>,
	Jiri Kosina <trivial@kernel.org>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH trivial next 7/9] scsi: Use vsprintf extention %pf with builtin_return_address
Date: Tue, 28 Feb 2012 10:49:36 -0800	[thread overview]
Message-ID: <aa5a8942edf8a59745a514a099e78eaaae03fe26.1330454853.git.joe@perches.com> (raw)
In-Reply-To: <cover.1330454853.git.joe@perches.com>

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>
---
 drivers/scsi/esp_scsi.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/scsi/esp_scsi.c b/drivers/scsi/esp_scsi.c
index 394ed9e..34552bf 100644
--- a/drivers/scsi/esp_scsi.c
+++ b/drivers/scsi/esp_scsi.c
@@ -1000,7 +1000,7 @@ static int esp_check_spur_intr(struct esp *esp)
 
 static void esp_schedule_reset(struct esp *esp)
 {
-	esp_log_reset("ESP: esp_schedule_reset() from %p\n",
+	esp_log_reset("ESP: esp_schedule_reset() from %pf\n",
 		      __builtin_return_address(0));
 	esp->flags |= ESP_FLAG_RESETTING;
 	esp_event(esp, ESP_EVENT_RESET);
-- 
1.7.8.111.gad25c.dirty


  parent reply	other threads:[~2012-02-28 18:50 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 ` Joe Perches [this message]
2012-02-28 21:07   ` [PATCH trivial next 7/9] scsi: " 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=aa5a8942edf8a59745a514a099e78eaaae03fe26.1330454853.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=JBottomley@parallels.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

all inboxes | Powered by JetHome®