From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Cc: Matt Mackall <mpm@selenic.com>, Neil Brown <neilb@suse.de>,
Laurent Pinchart <laurent.pinchart@skynet.be>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Steven Whitehouse <swhiteho@redhat.com>,
Artem Bityutskiy <dedekind@infradead.org>,
Adrian Hunter <adrian.hunter@nokia.com>,
Alex Elder <aelder@sgi.com>,
xfs-masters@oss.sgi.com, linux-raid@vger.kernel.org,
linux-media@vger.kernel.org, cluster-devel@redhat.com,
linux-mtd@lists.infradead.org, xfs@oss.sgi.com
Subject: [PATCH 0/8] Add vsprintf extension %pU to print UUID/GUIDs and use it
Date: Tue, 6 Oct 2009 21:45:33 -0700 [thread overview]
Message-ID: <1254890742-28245-1-git-send-email-joe@perches.com> (raw)
Using %pU makes an x86 defconfig image a bit smaller
before: $ size vmlinux
text data bss dec hex filename
6976022 679572 1359668 9015262 898fde vmlinux
after: $ size vmlinux
text data bss dec hex filename
6975863 679652 1359668 9015183 898f8f vmlinux
Joe Perches (8):
lib/vsprintf.c: Add %pU to print UUID/GUIDs
random.c: Use %pU to print UUIDs
drivers/firmware/dmi_scan.c: Use %pUB to print UUIDs
drivers/md/md.c: Use %pU to print UUIDs
drivers/media/video/uvc: Use %pUl to print UUIDs
fs/gfs2/sys.c: Use %pUB to print UUIDs
fs/ubifs: Use %pUB to print UUIDs
fs/xfs/xfs_log_recover.c: Use %pU to print UUIDs
drivers/char/random.c | 10 +---
drivers/firmware/dmi_scan.c | 5 +--
drivers/md/md.c | 16 ++------
drivers/media/video/uvc/uvc_ctrl.c | 69 ++++++++++++++++------------------
drivers/media/video/uvc/uvc_driver.c | 7 +--
drivers/media/video/uvc/uvcvideo.h | 10 -----
fs/gfs2/sys.c | 16 +------
fs/ubifs/debug.c | 9 +---
fs/ubifs/super.c | 7 +---
fs/xfs/xfs_log_recover.c | 14 ++-----
lib/vsprintf.c | 62 ++++++++++++++++++++++++++++++-
11 files changed, 114 insertions(+), 111 deletions(-)
next reply other threads:[~2009-10-07 4:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 4:45 Joe Perches [this message]
[not found] ` <cover.1254884776.git.joe@perches.com>
2009-10-07 4:45 ` [PATCH 1/8] lib/vsprintf.c: Add %pU to print UUID/GUIDs Joe Perches
2009-10-07 4:45 ` [PATCH 2/8] random.c: Use %pU to print UUIDs Joe Perches
2009-10-07 5:19 ` Matt Mackall
2009-10-07 4:45 ` [PATCH 3/8] drivers/firmware/dmi_scan.c: Use %pUB " Joe Perches
2009-10-07 4:45 ` [PATCH 4/8] drivers/md/md.c: Use %pU " Joe Perches
2009-10-07 4:45 ` [PATCH 5/8] drivers/media/video/uvc: Use %pUl " Joe Perches
2009-10-11 22:34 ` Laurent Pinchart
2009-10-31 9:07 ` Mauro Carvalho Chehab
2009-10-31 19:10 ` Laurent Pinchart
2009-10-31 19:27 ` Joe Perches
2009-11-04 14:42 ` Laurent Pinchart
2009-11-04 16:42 ` Joe Perches
2009-10-07 4:45 ` [PATCH 6/8] fs/gfs2/sys.c: Use %pUB " Joe Perches
2009-10-07 4:45 ` [PATCH 7/8] fs/ubifs: " Joe Perches
2009-10-07 4:45 ` [PATCH 8/8] fs/xfs/xfs_log_recover.c: Use %pU " Joe Perches
2009-10-07 6:11 ` [PATCH 9/8] efi.h: Use %pUl " Joe Perches
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=1254890742-28245-1-git-send-email-joe@perches.com \
--to=joe@perches.com \
--cc=adrian.hunter@nokia.com \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=dedekind@infradead.org \
--cc=laurent.pinchart@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mpm@selenic.com \
--cc=neilb@suse.de \
--cc=swhiteho@redhat.com \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.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®