From: Kalle Valo <kvalo@codeaurora.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>,
<davem@davemloft.net>
Subject: Re: [PATCH -next] ath10k: Fix W=1 build warning in htt_rx.c
Date: Sat, 12 Jun 2021 10:38:35 +0000 (UTC) [thread overview]
Message-ID: <20210612103835.018C4C4338A@smtp.codeaurora.org> (raw)
In-Reply-To: <20210526142219.2542528-1-yangyingliang@huawei.com>
Yang Yingliang <yangyingliang@huawei.com> wrote:
> Fix the following W=1 build warning:
>
> drivers/net/wireless/ath/ath10k/htt_rx.c:1790:7: warning: variable ‘more_frags’ set but not used [-Wunused-but-set-variable]
> 1790 | bool more_frags;
> | ^~~~~~~~~~
>
> Fixes: a1166b2653db ("ath10k: add CCMP PN replay protection for fragmented frames for PCIe")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
e0a6120f6816 ath10k: remove unused more_frags variable
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210526142219.2542528-1-yangyingliang@huawei.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2021-06-12 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 14:22 [PATCH -next] ath10k: Fix W=1 build warning in htt_rx.c Yang Yingliang
2021-05-26 14:22 ` Yang Yingliang
2021-06-12 10:38 ` Kalle Valo
2021-06-12 10:38 ` 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=20210612103835.018C4C4338A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@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.