All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 3/7] common/vsprintf: Add %ps and %pS format specifier support
Date: Tue, 5 Nov 2013 10:43:48 +0000	[thread overview]
Message-ID: <5278CBE4.7010605@citrix.com> (raw)
In-Reply-To: <1383647992.13961.42.camel@kazak.uk.xensource.com>

On 05/11/13 10:39, Ian Campbell wrote:
> On Mon, 2013-11-04 at 21:30 +0000, Andrew Cooper wrote:
>> +All parameters to a %p option should be enclosed with the _p() macro
> For numerical arguments, sure. Why for things that are already pointers?

GCC seemed funny about implicitly casting pointers to void* as far as
formatting went.  I will verify what the behaviour is on something modern.

>
>> +Symbol/Function pointers:
>> +
>> +       %ps     Symbol name only
>> +       %pS     Symbol name + offset / function length
> Perhaps give examples?

ok

>
>> +       In the case that an appropriate symbol name can't be found, %p[sS] will
>> +       fall back to '%p' and print the address in hex.
> In the common case the hex value will already be printed previously, but
> I suppose this is harmless.
>
> Ian.
>

print_symbol() would result in "???" if it failed to get a name.  Now,
we fall through to printing the hex address instead.

~Andrew

  reply	other threads:[~2013-11-05 10:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 21:30 [PATCH v2 0/7] Printk symbol specifier Andrew Cooper
2013-11-04 21:30 ` [PATCH 1/7] common/vsprintf: Refactor string() out of vsnprintf() Andrew Cooper
2013-11-04 21:30 ` [PATCH 2/7] common/vsprintf: Refactor pointer() " Andrew Cooper
2013-11-05 10:21   ` Jan Beulich
2013-11-05 10:25     ` Andrew Cooper
2013-11-04 21:30 ` [PATCH 3/7] common/vsprintf: Add %ps and %pS format specifier support Andrew Cooper
2013-11-05 10:39   ` Ian Campbell
2013-11-05 10:43     ` Andrew Cooper [this message]
2013-11-05 10:40   ` Jan Beulich
2013-11-05 10:57     ` Andrew Cooper
2013-11-04 21:30 ` [PATCH 4/7] x86: Replace print_symbol() with new %ps/%pS format Andrew Cooper
2013-11-05 10:47   ` Jan Beulich
2013-11-05 10:52     ` Andrew Cooper
2013-11-05 11:14       ` Jan Beulich
2013-11-05 11:16         ` Andrew Cooper
2013-11-04 21:30 ` [PATCH 5/7] arm: " Andrew Cooper
2013-11-04 21:30 ` [PATCH 6/7] common/symbols: Remove print_symbol() and associated infrastructure Andrew Cooper
2013-11-04 21:30 ` [PATCH 7/7] Test harness for new printk formatting Andrew Cooper

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=5278CBE4.7010605@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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.