All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cheng-wei Lee <lee.rhapsody@gmail.com>
Cc: johannes.berg@intel.com, josh@joshtriplett.org,
	sarah.a.sharp@linux.intel.com, himangi774@gmail.com,
	teobaluta@gmail.com, linville@tuxdriver.com, gamerh2o@gmail.com,
	devel <devel@driverdev.osuosl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: staging: wlan-ng: fix sparse warnings
Date: Wed, 8 Oct 2014 15:57:25 -0700	[thread overview]
Message-ID: <20141008225725.GA10158@kroah.com> (raw)
In-Reply-To: <542F5A5C.9050905@gmail.com>

On Sat, Oct 04, 2014 at 10:24:28AM +0800, Cheng-wei Lee wrote:
> This patch fix the sparse warnings in wlan-ng/cfg80211.c
> The following functions were only used in this file, so done by
> declaring them into static.
> 
> drivers/staging/wlan-ng/cfg80211.c:710:6: warning: symbol
> 'prism2_connect_result' was not declared. Should it be static?
> drivers/staging/wlan-ng/cfg80211.c:719:6: warning: symbol
> 'prism2_disconnected' was not declared. Should it be static?
> drivers/staging/wlan-ng/cfg80211.c:725:6: warning: symbol
> 'prism2_roamed' was not declared. Should it be static?
> 
> Signed-off-by: Quentin Lee <lee.rhapsody@gmail.com>
> ---
>  drivers/staging/wlan-ng/cfg80211.c |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

This patch doesn't apply to my staging-testing branch of staging.git,
can you refresh it and resend please?

thanks,

greg k-h

  reply	other threads:[~2014-10-08 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04  2:24 [PATCH] drivers: staging: wlan-ng: fix sparse warnings Cheng-wei Lee
2014-10-08 22:57 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-26 10:48 Cheng-Wei Lee
2014-09-26 11:02 ` Dan Carpenter

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=20141008225725.GA10158@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gamerh2o@gmail.com \
    --cc=himangi774@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=josh@joshtriplett.org \
    --cc=lee.rhapsody@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=teobaluta@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 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.