From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 23/23] drivers/net/wireless/mediatek/mt76/mt7925/main.c:2232:12: warning: variable 'link_id' set but not used
Date: Thu, 03 Sep 2026 11:30:35 +0800 [thread overview]
Message-ID: <202609031155.OwLcYxEa-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 3ef53509d71662f4219fbd3b7e07ec24c6fe56a8
commit: 3ef53509d71662f4219fbd3b7e07ec24c6fe56a8 [23/23] BACKPORT: wifi: mt76: mt7925: introduce CSA support in non-MLO mode
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20260903/202609031155.OwLcYxEa-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260903/202609031155.OwLcYxEa-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609031155.OwLcYxEa-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/wireless/mediatek/mt76/mt7925/main.c: In function 'mt7925_csa_work':
>> drivers/net/wireless/mediatek/mt76/mt7925/main.c:2232:12: warning: variable 'link_id' set but not used [-Wunused-but-set-variable=]
2232 | u8 link_id, roc_rtype;
| ^~~~~~~
vim +/link_id +2232 drivers/net/wireless/mediatek/mt76/mt7925/main.c
2224
2225 void mt7925_csa_work(struct work_struct *work)
2226 {
2227 struct mt792x_vif *mvif;
2228 struct mt792x_dev *dev;
2229 struct ieee80211_vif *vif;
2230 struct ieee80211_bss_conf *link_conf;
2231 struct mt792x_bss_conf *mconf;
> 2232 u8 link_id, roc_rtype;
2233 int ret = 0;
2234
2235 mvif = (struct mt792x_vif *)container_of(work, struct mt792x_vif,
2236 csa_work);
2237 dev = mvif->phy->dev;
2238 vif = container_of((void *)mvif, struct ieee80211_vif, drv_priv);
2239
2240 if (ieee80211_vif_is_mld(vif))
2241 return;
2242
2243 if (!dev->new_ctx)
2244 return;
2245
2246 link_id = 0;
2247 mconf = &mvif->bss_conf;
2248 link_conf = &vif->bss_conf;
2249 roc_rtype = MT7925_ROC_REQ_JOIN;
2250
2251 mt792x_mutex_acquire(dev);
2252 ret = mt7925_set_roc(mvif->phy, mconf, dev->new_ctx->def.chan,
2253 4000, roc_rtype);
2254 mt792x_mutex_release(dev);
2255 if (!ret) {
2256 mt792x_mutex_acquire(dev);
2257 ret = mt7925_mcu_set_chctx(mvif->phy->mt76, &mconf->mt76, link_conf,
2258 dev->new_ctx);
2259 mt792x_mutex_release(dev);
2260
2261 mt7925_abort_roc(mvif->phy, mconf);
2262 }
2263
2264 ieee80211_chswitch_done(vif, !ret);
2265 }
2266
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-03 3:30 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=202609031155.OwLcYxEa-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.