All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Kirtika Ruchandani <kirtika.ruchandani@gmail.com>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-wireless@vger.kernel.org,
	Nishant Sarmukadam <nishants@marvell.com>,
	Zhaoyang Liu <liuzy@marvell.com>, Bing Zhao <bzhao@marvell.com>,
	Xinming Hu <huxm@marvell.com>, Avinash Patil <patila@marvell.com>
Subject: Re: [v2, 1/7] mwifiex: Removed unused mwifiex_private* 'priv' variable
Date: Tue, 29 Nov 2016 15:28:16 +0000 (UTC)	[thread overview]
Message-ID: <20161129152816.14B74612BA@smtp.codeaurora.org> (raw)
In-Reply-To: <fa8a77df4638cf21720d8c5094afb83475947843.1479950323.git.kirtika@google.com>

Kirtika Ruchandani <kirtika.ruchandani@gmail.com> wrote:
> Commit bec568ff5107 removed the last remaining usage of struct
> mwifiex_private* priv in mwifiex_fw_dpc(), by removing the call to
> mwifiex_del_virtual_intf().
> Compiling mwifiex/ with W=1 gives the following warning, fix it.
> mwifiex/main.c: In function ‘mwifiex_fw_dpc’:
> mwifiex/main.c:520:26: warning: variable ‘priv’ set but not used [-Wunused-but-set-variable]
> 
> Fixes: bec568ff5107 ("mwifiex: failure path handling in mwifiex_add_virtual_intf()")
> Cc: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Kirtika Ruchandani <kirtika@google.com>

7 patches applied to wireless-drivers-next.git, thanks.

70d740598713 mwifiex: Removed unused mwifiex_private* 'priv' variable
8ac9134161d9 mwifiex: Remove unused 'chan_num' variable
2c2bcabf02e1 mwifiex: Remove unused 'sta_ptr' variable
60261b266a84 mwifiex: Remove unused 'adapter'variable
e9f1db8b6859 mwifiex: Remove unused 'pm_flag' variable
67dd2a754906 mwifiex: Removed unused 'pkt_type' variable
4133828c76c3 mwifiex: Remove unused 'bcd_usb' variable

-- 
https://patchwork.kernel.org/patch/9444651/

Documentation about submitting wireless patches and checking status
from patchwork:

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2016-11-29 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  1:24 [PATCH v2 0/7] Fix -Wunused-but-set-variable in mwifiex/ Kirtika Ruchandani
2016-11-24  1:24 ` [PATCH v2 1/7] mwifiex: Removed unused mwifiex_private* 'priv' variable Kirtika Ruchandani
2016-11-29 15:28   ` Kalle Valo [this message]
2016-11-24  1:24 ` [PATCH v2 2/7] mwifiex: Remove unused 'chan_num' variable Kirtika Ruchandani
2016-11-24  1:25 ` [PATCH v2 3/7] mwifiex: Remove unused 'sta_ptr' variable Kirtika Ruchandani
2016-11-24  1:25 ` [PATCH v2 4/7] mwifiex: Remove unused 'adapter'variable Kirtika Ruchandani
2016-11-24  1:26 ` [PATCH v2 5/7] mwifiex: Remove unused 'pm_flag' variable Kirtika Ruchandani
2016-11-24  1:26 ` [PATCH v2 6/7] mwifiex: Removed unused 'pkt_type' variable Kirtika Ruchandani
2016-11-24  1:27 ` [PATCH v2 7/7] mwifiex: Remove unused 'bcd_usb' variable Kirtika Ruchandani
2016-11-24  7:44 ` [PATCH v2 0/7] Fix -Wunused-but-set-variable in mwifiex/ Amitkumar Karwar

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=20161129152816.14B74612BA@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=arnd@arndb.de \
    --cc=bzhao@marvell.com \
    --cc=huxm@marvell.com \
    --cc=kirtika.ruchandani@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liuzy@marvell.com \
    --cc=nishants@marvell.com \
    --cc=patila@marvell.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.