netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Miller <davem@davemloft.net>,
	kaber@trash.net, harvey.harrison@gmail.com,
	netdev@vger.kernel.org
Subject: Re: New sparse warning in net/mac80211/debugfs_sta.c
Date: Mon, 25 Feb 2008 08:53:49 -0800	[thread overview]
Message-ID: <1203958429.19319.273.camel@localhost> (raw)
In-Reply-To: <1203933228.13162.58.camel@johannes.berg>

On Mon, 2008-02-25 at 10:53 +0100, Johannes Berg wrote:
> Maybe we should just add a new printf modifier like %M for MAC
> addresses? Then we could use sprintf, snprintf, printk and whatever we
> please without any of the macro stuff...

Could gcc validate the printf %M arguments?

Another possibility without changing printf argument validation
is to use a MAC_FMT macro in place of "%s"

#ifdef CONFIG_INLINE_MAC

#define MAC_FMT "%02x:%02x:%02x:%02x:%02x:%02x"
#define DECLARE_MAC_BUF(var)
#define print_mac(buf, addr) (addr)[0], (addr)[1], (addr)[2], (addr)[3], (addr)[4], (addr)[5]

#else

#define MAC_FMT "%s"
#define DECLARE_MAC_BUF(var) char var[18];
extern char *print_mac(char *buf, const unsigned char *addr);

#endif

use:

DECLARE_MAC_BUF(mac);
printk(KERN_INFO "Mac address is: " MAC_FMT "\n", print_mac(mac, addr));


  reply	other threads:[~2008-02-25 16:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  9:34 New sparse warning in net/mac80211/debugfs_sta.c Harvey Harrison
2008-02-21  9:54 ` Johannes Berg
2008-02-21 10:03   ` David Miller
2008-02-21 10:08     ` Harvey Harrison
2008-02-21 10:12       ` David Miller
2008-02-21 10:16         ` Harvey Harrison
2008-02-21 10:22           ` [PATCH] mac80211: fix debugfs_sta print_mac() warning Johannes Berg
     [not found] ` <20080221.015743.222059206.davem@davemloft.net>
2008-02-21 10:01   ` New sparse warning in net/mac80211/debugfs_sta.c Harvey Harrison
2008-02-21 10:05     ` David Miller
2008-02-21 10:14       ` Harvey Harrison
2008-02-21 10:17       ` Johannes Berg
2008-02-21 17:54         ` Joe Perches
2008-02-21 18:00           ` Patrick McHardy
2008-02-21 18:15             ` Patrick McHardy
2008-02-24  4:02             ` David Miller
2008-02-25  9:53               ` Johannes Berg
2008-02-25 16:53                 ` Joe Perches [this message]
2008-02-25 17:29                   ` Johannes Berg
2008-02-25 17:23                 ` Johannes Berg
2008-02-25 19:52                 ` David Miller
2008-02-25 19:56                   ` Johannes Berg
2008-02-25 20:05                     ` Johannes Berg
2008-02-25 20:14                       ` David Miller
2008-02-25 20:12                     ` David Miller
2008-02-25 11:47               ` Patrick McHardy
2008-02-25 19:58                 ` Joe Perches
2008-04-08 20:18                   ` Patrick McHardy
2008-04-08 21:02                     ` Joe Perches
2008-04-08 21:16                       ` David Miller
2008-04-08 21:19                       ` Patrick McHardy
2008-04-08 22:09                         ` Joe Perches
2008-04-08 22:30                           ` David Miller
2008-04-08 22:41                             ` Joe Perches
2008-04-08 22:32                           ` Patrick McHardy
2008-02-21 17:17       ` Joe Perches
2008-02-21 17:45       ` Patrick McHardy

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=1203958429.19319.273.camel@localhost \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=harvey.harrison@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kaber@trash.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 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).