From: Joe Perches <joe@perches.com>
To: Joel Pelaez Jorge <joelpelaez@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Silvan Jegen <s.jegen@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Staging: rtl8192e: Fix sparse warning
Date: Sun, 06 Apr 2014 12:02:42 -0700 [thread overview]
Message-ID: <1396810962.2874.11.camel@joe-AO722> (raw)
In-Reply-To: <5341A43A.3020200@gmail.com>
On Sun, 2014-04-06 at 14:00 -0500, Joel Pelaez Jorge wrote:
> El 06/04/14 13:49, Joe Perches escribió:
> > On Sun, 2014-04-06 at 13:43 -0500, Joel Pelaez Jorge wrote:
[]
> >> diff --git a/drivers/staging/rtl8192e/rtl8192e/rtl_wx.c
[]
> >> -static struct iw_statistics *r8192_get_wireless_stats(struct net_device
> >> *dev)
> >> +struct iw_statistics *r8192_get_wireless_stats(struct net_device *dev)
> >> {
> >> struct r8192_priv *priv = rtllib_priv(dev);
> >> struct rtllib_device *ieee = priv->rtllib;
> >
> > As far as I can tell, there's no reason this should
> > be declared in the .h file and it should stay static
> > and not be exposed at all.
[]
> In the source "rtl_core.c" is possible to use the symbol
> r8192_get_wireless_stats, if WIRELESS_EXT has specifics values.
>
> Although this scenario is unlikely to happen, is better prepare
> this code for it.
Huh? This makes no sense to me.
Maybe you can expand a bit here.
> Also, a better way will be delete 'extern' reference to symbol
> in header file and source file.
That's what I said.
next prev parent reply other threads:[~2014-04-06 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 18:43 Joel Pelaez Jorge
2014-04-06 18:49 ` Joe Perches
2014-04-06 19:00 ` Joel Pelaez Jorge
2014-04-06 19:02 ` Joe Perches [this message]
2014-04-06 19:01 ` Greg Kroah-Hartman
2014-04-06 19:12 ` Joel Pelaez Jorge
2014-04-06 20:26 ` Greg Kroah-Hartman
2014-04-06 20:43 ` Joel Pelaez Jorge
2014-04-06 20:59 ` Greg Kroah-Hartman
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=1396810962.2874.11.camel@joe-AO722 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joelpelaez@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.jegen@gmail.com \
/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®