From: kernel test robot <lkp@intel.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10358/12085] drivers/net/wireless/mediatek/mt76/tx.c:499:21: warning: variable 'q' set but not used
Date: Thu, 10 Dec 2020 00:35:49 +0800 [thread overview]
Message-ID: <202012100045.V7QIVRim-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2f1d5c77f13fe64497c2e2601605f7d7ec4da9b1
commit: 90d494c99a99fa2eb858754345c4a9c851b409a0 [10358/12085] mt76: improve tx queue stop/wake
config: parisc-randconfig-r033-20201209 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=90d494c99a99fa2eb858754345c4a9c851b409a0
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 90d494c99a99fa2eb858754345c4a9c851b409a0
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
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;
| ^
vim +/q +499 drivers/net/wireless/mediatek/mt76/tx.c
496
497 void mt76_txq_schedule(struct mt76_phy *phy, enum mt76_txq_id qid)
498 {
> 499 struct mt76_queue *q;
500 int len;
501
502 if (qid >= 4)
503 return;
504
505 q = phy->q_tx[qid];
506
507 rcu_read_lock();
508
509 do {
510 ieee80211_txq_schedule_start(phy->hw, qid);
511 len = mt76_txq_schedule_list(phy, qid);
512 ieee80211_txq_schedule_end(phy->hw, qid);
513 } while (len > 0);
514
515 rcu_read_unlock();
516 }
517 EXPORT_SYMBOL_GPL(mt76_txq_schedule);
518
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28901 bytes --]
reply other threads:[~2020-12-09 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202012100045.V7QIVRim-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=nbd@nbd.name \
/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