From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Xen-devel <xen-devel@lists.xen.org>,
Julien Grall <julien.grall@arm.com>,
Dario Faggioli <dfaggioli@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH 1/6] xen/vsprintf: Introduce %*pb[l] for printing bitmaps
Date: Tue, 25 Sep 2018 14:06:09 +0100 [thread overview]
Message-ID: <e1719883-6217-722f-dba7-a8526b14f035@citrix.com> (raw)
In-Reply-To: <5B9295CD02000078001E6723@prv1-mh.provo.novell.com>
On 07/09/18 16:14, Jan Beulich wrote:
>> Irrespective of whether you think it is ambiguous or not, I don't view
>> this as a good enough (potential) issue to diverge.
>>
>> Furthermore, (and more likely to sway your opinion), N1570 indicates
>> that the 'l' length modifier is only applicable for the diouxXcs
>> conversion specifiers, and both Clang and GCC enforce this with -Wformat.
>>
>> andrewcoop@andrewcoop:/local/xen.git/xen$ clang-6.0 -Wall -Werror -Wextra
>> foo.c -o foo.o
>> foo.c:7:22: error: length modifier 'l' results in undefined behavior or no
>> effect with 'p' conversion specifier [-Werror,-Wformat]
>> printf("Testing %lpd\n", ptr);
>> ~^~
>> 1 error generated.
> Yeah, I started to be concerned of this happening after I had sent
> the reply. Given this I guess we have no (good) choice besides going
> the suffix route.
So can I take this as at least an ack? Currently this series is stalled.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-25 13:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 12:08 [PATCH 0/6] xen: Use %*pb[l] for printing bitmaps Andrew Cooper
2018-09-06 12:08 ` [PATCH 1/6] xen/vsprintf: Introduce " Andrew Cooper
2018-09-06 16:32 ` Wei Liu
2018-09-07 7:41 ` Jan Beulich
2018-09-07 13:01 ` Andrew Cooper
2018-09-07 15:14 ` Jan Beulich
2018-09-25 13:06 ` Andrew Cooper [this message]
2018-09-25 13:22 ` Jan Beulich
2018-09-06 12:08 ` [PATCH 2/6] xen/sched: Use %*pb[l] instead of cpumask_scn{, list}printf() Andrew Cooper
2018-09-07 8:03 ` Jan Beulich
2018-09-07 13:56 ` Andrew Cooper
2018-09-07 14:42 ` George Dunlap
2018-09-07 15:17 ` Jan Beulich
2018-09-07 15:35 ` George Dunlap
2018-09-07 15:53 ` Jan Beulich
2018-09-07 16:07 ` Andrew Cooper
2018-09-10 6:39 ` Jan Beulich
2018-09-07 14:42 ` George Dunlap
2018-09-12 8:05 ` Dario Faggioli
2018-09-06 12:08 ` [PATCH 3/6] xen/common: Use %*pb[l] instead of {cpu, node}mask_scn{, list}printf() Andrew Cooper
2018-09-06 16:32 ` Wei Liu
2018-09-07 8:06 ` Jan Beulich
2018-09-07 8:30 ` Juergen Gross
2018-09-06 12:08 ` [PATCH 4/6] xen/x86: Use %*pb[l] instead of cpumask_scn{, list}printf() Andrew Cooper
2018-09-06 16:33 ` Wei Liu
2018-09-07 8:12 ` Jan Beulich
2018-09-07 14:00 ` Andrew Cooper
2018-09-06 12:08 ` [PATCH 5/6] xen/bitmap: Drop all bitmap_scn{, list}printf() infrastructure Andrew Cooper
2018-09-06 16:34 ` Wei Liu
2018-09-12 8:09 ` Dario Faggioli
2018-09-06 12:08 ` [PATCH RFC 6/6] xen/keyhandler: Drop keyhandler_scratch Andrew Cooper
2018-09-06 16:31 ` Wei Liu
2018-09-07 8:24 ` Jan Beulich
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=e1719883-6217-722f-dba7-a8526b14f035@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dfaggioli@suse.com \
--cc=julien.grall@arm.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--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 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).