public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "L. Alberto Giménez" <agimenez@sysvalve.es>
Cc: devel@driverdev.osuosl.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8172u: Make ieee80211_crypto_init static
Date: Sat, 21 Jun 2014 13:16:46 -0700	[thread overview]
Message-ID: <20140621201646.GB20432@kroah.com> (raw)
In-Reply-To: <20140621100444.GA31059@bart.evergreen.loc>

On Sat, Jun 21, 2014 at 12:04:44PM +0200, L. Alberto Giménez wrote:
> On Thu, Jun 19, 2014 at 05:14:26PM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Jun 12, 2014 at 07:40:49PM +0200, L. Alberto Giménez wrote:
> > > Fix sparse warning.
> > > 
> > > Signed-off-by: L. Alberto Giménez <agimenez@sysvalve.es>
> > > ---
> > >  drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> > > index 5533221..3be690d 100644
> > > --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> > > +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> > > @@ -200,7 +200,7 @@ static struct ieee80211_crypto_ops ieee80211_crypt_null = {
> > >  	.owner			= THIS_MODULE,
> > >  };
> > >  
> > > -int __init ieee80211_crypto_init(void)
> > > +static int __init ieee80211_crypto_init(void)
> > >  {
> > >  	int ret = -ENOMEM;
> > 
> > You obviously did not compile this change :(
> > 
> > greg k-h
> 
> Hi Greg,
> 
> I'm very sorry for that, I swear I compiled it, but clearly I'm missing something
> here.
> 
> My patch compiles with a warning, but tag v3.15 (tag where my branch is based) does
> not issue this warning:
> 
> drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c:203:19: warning:
> ‘ieee80211_crypto_init’ defined but not used [-Wunused-function]
>  static int __init ieee80211_crypto_init(void)
>                    ^
> 
> I thought that __init functions could be static, is there any problem with that? Care
> to shed some light here?

That function is called by a different file, it can not be static, I
don't know how you were able to successfully build the driver with your
change...

      reply	other threads:[~2014-06-21 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 17:40 [PATCH] staging: rtl8172u: Make ieee80211_crypto_init static L. Alberto Giménez
2014-06-20  0:14 ` Greg Kroah-Hartman
2014-06-21 10:04   ` L. Alberto Giménez
2014-06-21 20:16     ` Greg Kroah-Hartman [this message]

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=20140621201646.GB20432@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=agimenez@sysvalve.es \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@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