From: Kalle Valo <kvalo@codeaurora.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: remove set but not used variable 'tlv_len'
Date: Mon, 5 Nov 2018 11:13:27 +0000 (UTC) [thread overview]
Message-ID: <20181105111327.9763260600@smtp.codeaurora.org> (raw)
In-Reply-To: <1539951626-185764-1-git-send-email-yuehaibing@huawei.com>
YueHaibing <yuehaibing@huawei.com> wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/ath/ath10k/wmi-tlv.c: In function 'ath10k_wmi_tlv_op_gen_config_pno_start':
> drivers/net/wireless/ath/ath10k/wmi-tlv.c:3455:6: warning:
> variable 'tlv_len' set but not used [-Wunused-but-set-variable]
>
> It never used since inroduction in commit
> ce834e280f2f ("ath10k: support NET_DETECT WoWLAN feature")
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
3468404f78e1 ath10k: remove set but not used variable 'tlv_len'
--
https://patchwork.kernel.org/patch/10649069/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-11-05 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 12:20 [PATCH] ath10k: remove set but not used variable 'tlv_len' YueHaibing
2018-10-19 12:20 ` YueHaibing
2018-10-19 12:20 ` YueHaibing
2018-11-05 11:13 ` Kalle Valo [this message]
2018-11-05 11:13 ` Kalle Valo
2018-11-05 11:13 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2018-11-08 9:32 [PATCH] ath10k: remove set but not used variable 'num_tdls_vifs' YueHaibing
2018-11-08 9:32 ` YueHaibing
2018-11-08 9:32 ` YueHaibing
2018-12-20 16:47 ` Kalle Valo
2018-12-20 16:47 ` Kalle Valo
2018-12-20 16:47 ` Kalle Valo
2018-12-20 16:47 ` Kalle Valo
2018-12-20 16:47 ` Kalle Valo
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=20181105111327.9763260600@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yuehaibing@huawei.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.