From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH 2/7] common/vsprintf: Refactor pointer() out of vsnprintf()
Date: Tue, 5 Nov 2013 10:25:05 +0000 [thread overview]
Message-ID: <5278C781.50500@citrix.com> (raw)
In-Reply-To: <5278D4BE02000078000FF70E@nat28.tlf.novell.com>
On 05/11/13 10:21, Jan Beulich wrote:
>>>> On 04.11.13 at 22:30, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> No fuctional change
> functional
>
>> + str = number(str, end, val, 16, field_width, precision, flags);
>> +
>> + return str;
> Why not simply "return number(...);"?
I thought I did, although that appears to only have made it into the
subsequent patch.
>
>> @@ -399,13 +414,8 @@ int vsnprintf(char *buf, size_t size, const char *fmt, va_list args)
>> continue;
>>
>> case 'p':
>> - if (field_width == -1) {
>> - field_width = 2*sizeof(void *);
>> - flags |= ZEROPAD;
>> - }
>> - str = number(str, end,
>> - (unsigned long) va_arg(args, void *),
>> - 16, field_width, precision, flags);
>> + str = pointer(str, end, (unsigned long) va_arg(args, void *),
>> + field_width, precision, flags);
> The va_arg() result clearly shouldn't be cast here, even if both
> the use here and that added by the next patch require this. I'm
> definitely planning on adding a modifier to print domain/vcpu IDs
> as a pair from a single "struct vcpu *" argument, and such code
> shouldn't be required to cast back from "unsigned long" to a
> pointer.
>
> Jan
Ok - I will use a void* instead.
~Andrew
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-05 10:25 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 [this message]
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
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=5278C781.50500@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.