netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Joe Perches <joe@perches.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	David Miller <davem@davemloft.net>,
	harvey.harrison@gmail.com, netdev@vger.kernel.org
Subject: Re: New sparse warning in net/mac80211/debugfs_sta.c
Date: Thu, 21 Feb 2008 19:15:53 +0100	[thread overview]
Message-ID: <47BDBFD9.1080808@trash.net> (raw)
In-Reply-To: <47BDBC23.5080007@trash.net>

Patrick McHardy wrote:
> Joe Perches wrote:
>>
>> This removes the __pure from print_mac, so reject as appropriate...
>>
>> Add some type safety to print_mac by using struct print_mac_buf * 
>> instead of char *.
>
> And adds back the overhead of two completely unnecessary
> function calls to the VLAN fastpath. 

BTW, this also affects ATM, with 3 calls in hard_start_xmit,
3 calls in lec_xmit and 1 cakk in lec_atm_send.

> How about just
> stopping this idiocy and reverting the appropriate patches
> to bring back MAC_FMT and use it where appropriate? 


  reply	other threads:[~2008-02-21 18:16 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 [this message]
2008-02-24  4:02             ` David Miller
2008-02-25  9:53               ` Johannes Berg
2008-02-25 16:53                 ` Joe Perches
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=47BDBFD9.1080808@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=harvey.harrison@gmail.com \
    --cc=joe@perches.com \
    --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 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).