From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@nokia.com>,
Alex Elder <aelder@sgi.com>,
Artem Bityutskiy <dedekind@infradead.org>,
Christoph Hellwig <hch@lst.de>,
Harvey Harrison <harvey.harrison@gmail.com>,
Huang Ying <ying.huang@intel.com>, Ingo Molnar <mingo@elte.hu>,
Jeff Garzik <jgarzik@redhat.com>,
Laurent Pinchart <laurent.pinchart@skynet.be>,
Matt Mackall <mpm@selenic.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Neil Brown <neilb@suse.de>,
Steven Whitehouse <swhiteho@redhat.com>,
xfs-masters@oss.sgi.com, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/9] lib/vsprintf.c: Add %pU to print UUID/GUIDs
Date: Thu, 01 Oct 2009 00:26:40 -0700 [thread overview]
Message-ID: <1254382000.1799.13.camel@Joe-Laptop.home> (raw)
In-Reply-To: <10f740e80910010010o4522a008h265e09d7988d7192@mail.gmail.com>
On Thu, 2009-10-01 at 09:10 +0200, Geert Uytterhoeven wrote:
> > Standardize the printed style of UUID/GUIDs by using
> > another extension to %p.
> >
> > %pU: 01020304-0506-0708-090a-0b0c0d0e0f10
> > %pUr: 04030201-0605-0807-090a-0b0c0d0e0f10
> > %pU[r]X:Use upper case hex
>
> To me, it looks a bit strange to have the options after the `U', combined with
> the variable-length nature.
I think the whole %p<foo> mechanism is strange and takes
a bit of getting used to.
You're free to suggest alternatives.
Keep in mind expansion for future different types and that
<foo> must be alphanumeric chars only.
cheers, Joe
next prev parent reply other threads:[~2009-10-01 7:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 5:01 [PATCH 0/9] Add vsprintf extension %pU to print UUID/GUIDs and use it Joe Perches
2009-09-29 5:01 ` [PATCH 1/9] lib/vsprintf.c: Add %pU to print UUID/GUIDs Joe Perches
2009-10-01 7:10 ` Geert Uytterhoeven
2009-10-01 7:26 ` Joe Perches [this message]
2009-10-01 8:55 ` Geert Uytterhoeven
2009-10-07 0:07 ` Joe Perches
2009-09-29 5:01 ` [PATCH 2/9] efi.h: Use %pUr to print UUIDs Joe Perches
2009-09-29 5:01 ` [PATCH 3/9] random.c: Use %pU " Joe Perches
2009-09-29 5:01 ` [PATCH 4/9] drivers/firmware/dmi_scan.c: Use %pUX " Joe Perches
2009-09-29 5:01 ` [PATCH 5/9] drivers/md/md.c: Use %pU " Joe Perches
2009-09-29 5:01 ` [PATCH 6/9] drivers/media/video/uvc: Use %pUr " Joe Perches
2009-10-01 0:20 ` Laurent Pinchart
2009-10-01 0:24 ` Joe Perches
2009-09-29 5:01 ` [PATCH 7/9] fs/gfs2/sys.c: Use %pUX " Joe Perches
2009-09-29 8:50 ` Steven Whitehouse
2009-09-29 5:01 ` [PATCH 8/9] fs/ubifs: " Joe Perches
2009-09-29 12:32 ` Artem Bityutskiy
2009-09-29 5:01 ` [PATCH 9/9] fs/xfs/xfs_log_recover.c: Use %pU " Joe Perches
2009-09-29 5:57 ` [PATCH 0/9] Add vsprintf extension %pU to print UUID/GUIDs and use it Huang Ying
2009-10-01 0:07 ` Laurent Pinchart
2009-10-01 0:20 ` Joe Perches
2009-10-10 5:50 ` Huang Ying
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=1254382000.1799.13.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=adrian.hunter@nokia.com \
--cc=aelder@sgi.com \
--cc=davem@davemloft.net \
--cc=dedekind@infradead.org \
--cc=geert@linux-m68k.org \
--cc=harvey.harrison@gmail.com \
--cc=hch@lst.de \
--cc=jgarzik@redhat.com \
--cc=laurent.pinchart@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=neilb@suse.de \
--cc=swhiteho@redhat.com \
--cc=xfs-masters@oss.sgi.com \
--cc=ying.huang@intel.com \
/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®