From: Denis Vlasenko <vda@ilport.com.ua>
To: linux-kernel@vger.kernel.org
Cc: Adrian Bunk <bunk@stusta.de>, Jeff Garzik <jgarzik@pobox.com>
Subject: [PATCH] %n.n -> %0n printf format specifiers
Date: Fri, 26 Aug 2005 10:54:59 +0300 [thread overview]
Message-ID: <200508261055.00190.vda@ilport.com.ua> (raw)
Hi folks,
We have ~2k of printf format specs like this:
"%s: Transmit timed out, status %4.4x, PHY status %4.4x, resetting...\n"
IIRC %04x and %4.4x are totally equivalent. %04 is shorter.
Patches are at http://195.66.192.167/linux/printf_patch/
Largest ones are:
# ls -l | sort -r
total 1012
-rw-r--r-- 1 root root 11424 Aug 26 10:49 3c59x.c.patch
-rw-r--r-- 1 root root 8985 Aug 26 10:50 yellowfin.c.patch
-rw-r--r-- 1 root root 8692 Aug 26 10:50 lec.c.patch
-rw-r--r-- 1 root root 8619 Aug 26 10:50 hamachi.c.patch
-rw-r--r-- 1 root root 8571 Aug 26 10:49 3c515.c.patch
-rw-r--r-- 1 root root 7829 Aug 26 10:50 winbond-840.c.patch
-rw-r--r-- 1 root root 7526 Aug 26 10:50 eepro100.c.patch
-rw-r--r-- 1 root root 7456 Aug 26 10:50 virgefb.c.patch
-rw-r--r-- 1 root root 7255 Aug 26 10:50 epic100.c.patch
-rw-r--r-- 1 root root 6725 Aug 26 10:49 8139too.c.patch
-rw-r--r-- 1 root root 6448 Aug 26 10:50 pci-skeleton.c.patch
-rw-r--r-- 1 root root 6403 Aug 26 10:50 via-rhine.c.patch
-rw-r--r-- 1 root root 5944 Aug 26 10:50 sundance.c.patch
-rw-r--r-- 1 root root 5944 Aug 26 10:50 l2cap.c.patch
-rw-r--r-- 1 root root 5811 Aug 26 10:50 ixj.c.patch
-rw-r--r-- 1 root root 5052 Aug 26 10:50 xircom_tulip_cb.c.patch
-rw-r--r-- 1 root root 4991 Aug 26 10:50 tulip_core.c.patch
-rw-r--r-- 1 root root 4958 Aug 26 10:50 interrupt.c.patch
-rw-r--r-- 1 root root 4610 Aug 26 10:50 media.c.patch
-rw-r--r-- 1 root root 4449 Aug 26 10:50 depca.c.patch
-rw-r--r-- 1 root root 4281 Aug 26 10:49 3c509.c.patch
-rw-r--r-- 1 root root 4236 Aug 26 10:50 21142.c.patch
-rw-r--r-- 1 root root 3780 Aug 26 10:49 raw1394.c.patch
-rw-r--r-- 1 root root 3733 Aug 26 10:49 residual.c.patch
-rw-r--r-- 1 root root 3561 Aug 26 10:50 pnic2.c.patch
-rw-r--r-- 1 root root 3353 Aug 26 10:50 fealnx.c.patch
-rw-r--r-- 1 root root 3246 Aug 26 10:50 sis900.c.patch
-rw-r--r-- 1 root root 3193 Aug 26 10:50 pcnet32.c.patch
-rw-r--r-- 1 root root 3184 Aug 26 10:49 cdu31a.c.patch
-rw-r--r-- 1 root root 3122 Aug 26 10:50 smc91c92_cs.c.patch
...
Feel free to grab & apply to your driver(s).
--
vda
reply other threads:[~2005-08-26 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200508261055.00190.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®