From: Kalle Valo <kvalo@codeaurora.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: ryder.lee@mediatek.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org,
lorenzo.bianconi83@gmail.com, kuba@kernel.org,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org,
nbd@nbd.name
Subject: Re: [PATCH] mt76: Fixed kernel test robot warning
Date: Thu, 10 Dec 2020 09:16:23 +0200 [thread overview]
Message-ID: <87ft4e9lmg.fsf@codeaurora.org> (raw)
In-Reply-To: <1607542617-4005-1-git-send-email-jrdr.linux@gmail.com> (Souptick Joarder's message of "Thu, 10 Dec 2020 01:06:57 +0530")
Souptick Joarder <jrdr.linux@gmail.com> writes:
> Kernel test robot throws below warning ->
>
> drivers/net/wireless/mediatek/mt76/tx.c: In function
> 'mt76_txq_schedule':
>>> drivers/net/wireless/mediatek/mt76/tx.c:499:21: warning: variable 'q'
>>> set but not used [-Wunused-but-set-variable]
> 499 | struct mt76_queue *q;
> | ^
>
> This patch will silence this warning.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
I would like to take this directly to wireless-drivers-next, ok?
I'll also change the title to:
mt76: remove unused variable q
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-12-10 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 19:36 [PATCH] mt76: Fixed kernel test robot warning Souptick Joarder
2020-12-10 7:16 ` Kalle Valo [this message]
2020-12-11 6:51 ` Souptick Joarder
2020-12-11 18:28 ` mt76: remove unused variable q 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=87ft4e9lmg.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=davem@davemloft.net \
--cc=jrdr.linux@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ryder.lee@mediatek.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).