All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, netdev@vger.kernel.org
Subject: Re: New sparse warning in net/mac80211/debugfs_sta.c
Date: Thu, 21 Feb 2008 02:01:19 -0800	[thread overview]
Message-ID: <1203588079.20345.15.camel@brick> (raw)
In-Reply-To: <20080221.015743.222059206.davem@davemloft.net>

On Thu, 2008-02-21 at 01:57 -0800, David Miller wrote:
> From: Harvey Harrison <harvey.harrison@gmail.com>
> Date: Thu, 21 Feb 2008 01:34:27 -0800
> 
> > commit 0795af5729b18218767fab27c44b1384f72dc9ad
> > Author: Joe Perches <joe@perches.com>
> > Date:   Wed Oct 3 17:59:30 2007 -0700
> > 
> >     [NET]: Introduce and use print_mac() and DECLARE_MAC_BUF()
> >     
> >     This is nicer than the MAC_FMT stuff.
> >     
> >     Signed-off-by: Joe Perches <joe@perches.com>
> >     Signed-off-by: David S. Miller <davem@davemloft.net>
> > 
> > Introduced:
> > net/mac80211/debugfs_sta.c: In function ‘ieee80211_sta_debugfs_add’:
> > net/mac80211/debugfs_sta.c:211: warning: statement with no effect
> > 
> > Does print_mac modify the mac buffer in-place, or return a new buffer?
> 
> It modifies the buffer in place.
> 
> The warning is likely not from Joe's patch, but more likely
> from the __pure attribute I recently added to print_mac()'s
> declaration.  If so, we'll need to perhaps rework things.

In this case, it's being passed to a debugfs create function, could it
instead use sysfs_format_mac?

Harvey


  parent reply	other threads:[~2008-02-21 10:01 UTC|newest]

Thread overview: 37+ 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
2008-02-21 10:22             ` Johannes Berg
     [not found] ` <20080221.015743.222059206.davem@davemloft.net>
2008-02-21 10:01   ` Harvey Harrison [this message]
2008-02-21 10:05     ` New sparse warning in net/mac80211/debugfs_sta.c 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
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=1203588079.20345.15.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --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.