From: Kalle Valo <kvalo@codeaurora.org>
To: <Ajay.Kathat@microchip.com>
Cc: <linux-wireless@vger.kernel.org>, <Claudiu.Beznea@microchip.com>,
<Ajay.Kathat@microchip.com>, <lkp@intel.com>
Subject: Re: [PATCH] wilc1000: remove '-Wunused-but-set-variable' warning in chip_wakeup()
Date: Fri, 26 Nov 2021 16:33:02 +0000 (UTC) [thread overview]
Message-ID: <163794437900.10370.13472021044884634684.kvalo@codeaurora.org> (raw)
In-Reply-To: <20211115102809.1408267-1-ajay.kathat@microchip.com>
<Ajay.Kathat@microchip.com> wrote:
> From: Ajay Singh <ajay.kathat@microchip.com>
>
> Remove unused variables to avoid the below warnings:
>
> drivers/net/wireless/microchip/wilc1000/wlan.c: In function 'chip_wakeup':
> >> drivers/net/wireless/microchip/wilc1000/wlan.c:620:34: warning: variable 'to_host_from_fw_bit' set but not used [-Wunused-but-set-variable]
> 620 | u32 to_host_from_fw_reg, to_host_from_fw_bit;
> | ^~~~~~~~~~~~~~~~~~~
> >> drivers/net/wireless/microchip/wilc1000/wlan.c:620:13: warning: variable 'to_host_from_fw_reg' set but not used [-Wunused-but-set-variable]
> 620 | u32 to_host_from_fw_reg, to_host_from_fw_bit;
> | ^~~~~~~~~~~~~~~~~~~
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
Patch applied to wireless-drivers-next.git, thanks.
d1e69b5492d1 wilc1000: remove '-Wunused-but-set-variable' warning in chip_wakeup()
--
https://patchwork.kernel.org/project/linux-wireless/patch/20211115102809.1408267-1-ajay.kathat@microchip.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-11-26 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 10:28 [PATCH] wilc1000: remove '-Wunused-but-set-variable' warning in chip_wakeup() Ajay.Kathat
2021-11-26 16:33 ` Kalle Valo [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=163794437900.10370.13472021044884634684.kvalo@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Ajay.Kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.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).