linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Singh <ajay.kathat@microchip.com>
Cc: linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
	venkateswara.kaja@microchip.com, ganesh.krishna@microchip.com,
	adham.abozaeid@Microchip.com, aditya.shankar@microchip.com
Subject: Re: [PATCH v2 1/9] staging: wilc1000: remove unused global variables related to p2p
Date: Wed, 28 Mar 2018 13:35:56 +0200	[thread overview]
Message-ID: <20180328113556.GA30980@kroah.com> (raw)
In-Reply-To: <1522064763-11576-2-git-send-email-ajay.kathat@microchip.com>

On Mon, Mar 26, 2018 at 05:15:55PM +0530, Ajay Singh wrote:
> Cleanup patch to remove the unused global variables defined for p2p.
> 
> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
> Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
>  drivers/staging/wilc1000/host_interface.c | 59 -------------------------------
>  1 file changed, 59 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
> index 5082ede..a13998d 100644
> --- a/drivers/staging/wilc1000/host_interface.c
> +++ b/drivers/staging/wilc1000/host_interface.c
> @@ -254,13 +254,6 @@ static u32 inactive_time;
>  static u8 del_beacon;
>  static u32 clients_count;
>  
> -static u8 *join_req;
> -static u8 *info_element;
> -static u8 mode_11i;
> -static u8 auth_type;
> -static u32 join_req_size;
> -static u32 info_element_size;
> -static struct wilc_vif *join_req_vif;

These are not "globals", just static to this file.  But yeah, global to
the file, but when I think of "global", I think of "global to the whole
kernel".

Anyway, not a problem...

greg k-h

  reply	other threads:[~2018-03-28 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 11:45 [PATCH v2 0/9] staging: wilc1000: fix memory leaks and checkpatch reported issues Ajay Singh
2018-03-26 11:45 ` [PATCH v2 1/9] staging: wilc1000: remove unused global variables related to p2p Ajay Singh
2018-03-28 11:35   ` Greg KH [this message]
2018-03-26 11:45 ` [PATCH v2 2/9] staging: wilc1000: avoid 'NULL' pointer access in wilc_network_info_received() Ajay Singh
2018-03-26 11:45 ` [PATCH v2 3/9] staging: wilc1000: free allocated memory in edit and add station functions Ajay Singh
2018-03-26 11:45 ` [PATCH v2 4/9] staging: wilc1000: free memory allocated in add wep key functions Ajay Singh
2018-03-26 11:45 ` [PATCH v2 5/9] staging: wilc1000: free allocated memory after processing wilc_send_config_pkt() Ajay Singh
2018-03-26 11:46 ` [PATCH v2 6/9] staging: wilc1000: fix to free allocated memory in wilc_add_ptk() Ajay Singh
2018-03-26 11:46 ` [PATCH v2 7/9] staging: wilc1000: free allocated memory in wilc_add_rx_gtk() Ajay Singh
2018-03-26 11:46 ` [PATCH v2 8/9] staging: wilc1000: split handle_rcvd_gnrl_async_info() to avoid leading tabs Ajay Singh
2018-03-26 11:46 ` [PATCH v2 9/9] staging: wilc1000: free memory allocated for general info message from firmware Ajay Singh

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=20180328113556.GA30980@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adham.abozaeid@Microchip.com \
    --cc=aditya.shankar@microchip.com \
    --cc=ajay.kathat@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ganesh.krishna@microchip.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=venkateswara.kaja@microchip.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;
as well as URLs for NNTP newsgroup(s).