From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "David S. Miller" <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] add %pM printf format specifier
Date: Fri, 24 Oct 2008 18:41:45 -0700 [thread overview]
Message-ID: <1224898906.6636.74.camel@localhost> (raw)
In-Reply-To: <1224892008.3919.27.camel@johannes.berg>
On Sat, 2008-10-25 at 01:46 +0200, Johannes Berg wrote:
> This adds a new printf format specifier for the kernel, %pM,
> to be used to print out MAC addresses. This has advantages
> over the current print_mac scheme:
> * no need for DECLARE_MAC_BUF
> * can be used safely in statements that might be compiled
> out without the print_mac call staying.
Good things.
> --- everything.orig/lib/vsprintf.c 2008-10-25 01:21:54.000000000 +0200
> +++ everything/lib/vsprintf.c 2008-10-25 01:24:15.000000000 +0200
> @@ -581,6 +581,22 @@ static char *resource_string(char *buf,
> return string(buf, end, sym, field_width, precision, flags);
> }
>
> +static char *mac_address(char *buf, char *end, u8 *addr, int field_width, int precision, int flags)
> +{
> + /* room for 6 * two hex digits, 5 colons and trailing zero */
> + char mac[18];
> + char *p = mac, *pend = mac + sizeof(mac);
> + int i;
> +
> + for (i=0; i < 6; i++) {
> + p = number(p, pend, addr[i], 16, 2, -1, SMALL | ZEROPAD);
> + *p++ = ':';
> + }
For consistency, shouldn't the function name be mac_address_string?
I (and perhaps Harvey H) would be happier with:
char mac[18];
char *p = mac;
int i;
for (i = 0; i < 5; i++) {
p = pack_hex_byte(p, addr[i]);
*p++ = ':';
}
p = pack_hex_byte(p, addr[5]);
*p = '\0';
Smaller, faster, etc...
Also, as the number of %p(foo) types increases, perhaps
something like sparse could validate the printf argument
types?
cheers, Joe
next prev parent reply other threads:[~2008-10-25 1:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 23:46 [PATCH] add %pM printf format specifier Johannes Berg
2008-10-25 1:41 ` Joe Perches [this message]
2008-10-25 8:00 ` Johannes Berg
2008-10-25 17:44 ` Sven Anders
2008-10-26 8:01 ` Johannes Berg
2008-10-26 8:03 ` David Miller
2008-10-26 8:21 ` Johannes Berg
2008-10-26 8:30 ` Johannes Berg
2008-10-26 19:01 ` Harvey Harrison
2008-10-26 19:33 ` Johannes Berg
2008-10-26 19:38 ` Harvey Harrison
2008-10-26 19:40 ` Johannes Berg
2008-10-26 22:39 ` [RFC PATCH] printk: add the %pM, %p4, %p6 format specifiers Harvey Harrison
2008-10-27 0:31 ` [RFC PATCHv2] " Harvey Harrison
2008-10-27 1:21 ` Frans Pop
2008-10-27 2:08 ` H. Peter Anvin
2008-10-27 6:59 ` Johannes Berg
2008-10-27 16:28 ` Harvey Harrison
2008-10-27 19:38 ` David Miller
2008-10-27 19:47 ` Johannes Berg
2008-10-27 19:59 ` [RFC PATCHv3] printk: add %pM format specifier for MAC addresses Harvey Harrison
2008-10-27 21:55 ` Joe Perches
2008-10-27 22:46 ` David Miller
2008-10-27 22:47 ` David Miller
2008-10-27 23:14 ` Harvey Harrison
2008-10-27 23:31 ` Alexey Dobriyan
2008-10-27 23:48 ` Joe Perches
2008-10-28 8:04 ` Johannes Berg
2008-10-27 23:55 ` David Miller
2008-10-28 0:05 ` Harvey Harrison
2008-10-28 0:22 ` Joe Perches
2008-10-28 8:06 ` Johannes Berg
2008-10-26 8:38 ` [PATCH] add %pM printf format specifier Johannes Berg
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=1224898906.6636.74.camel@localhost \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=netdev@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 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.