From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-5.10 27/36] drivers/net/wireless/mediatek/mt76/mt7921/mcu.c:148:40: warning: variable 'res' set but not used
Date: Fri, 14 Apr 2023 00:30:25 +0800 [thread overview]
Message-ID: <202304140025.JDd41CCB-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.10
head: 44452e4236561f6e36ec587805a52b683e2804c9
commit: ba11d449cc75d38642771c4254d9ac6cca0dab30 [27/36] FROMLIST: mt76: mt7921: fix kernel panic by accessing unallocated eeprom.data
config: arc-randconfig-r043-20230409 (https://download.01.org/0day-ci/archive/20230414/202304140025.JDd41CCB-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.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
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-5.10
git checkout ba11d449cc75d38642771c4254d9ac6cca0dab30
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash M=drivers/net/wireless/mediatek/mt76/mt7921
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304140025.JDd41CCB-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/wireless/mediatek/mt76/mt7921/mcu.c: In function 'mt7921_mcu_parse_eeprom':
>> drivers/net/wireless/mediatek/mt76/mt7921/mcu.c:148:40: warning: variable 'res' set but not used [-Wunused-but-set-variable]
148 | struct mt7921_mcu_eeprom_info *res;
| ^~~
vim +/res +148 drivers/net/wireless/mediatek/mt76/mt7921/mcu.c
da3e3b87f8dd3d4 Sean Wang 2021-01-28 144
da3e3b87f8dd3d4 Sean Wang 2021-01-28 145 static int
da3e3b87f8dd3d4 Sean Wang 2021-01-28 146 mt7921_mcu_parse_eeprom(struct mt76_dev *dev, struct sk_buff *skb)
da3e3b87f8dd3d4 Sean Wang 2021-01-28 147 {
da3e3b87f8dd3d4 Sean Wang 2021-01-28 @148 struct mt7921_mcu_eeprom_info *res;
da3e3b87f8dd3d4 Sean Wang 2021-01-28 149
da3e3b87f8dd3d4 Sean Wang 2021-01-28 150 if (!skb)
da3e3b87f8dd3d4 Sean Wang 2021-01-28 151 return -EINVAL;
da3e3b87f8dd3d4 Sean Wang 2021-01-28 152
da3e3b87f8dd3d4 Sean Wang 2021-01-28 153 skb_pull(skb, sizeof(struct mt7921_mcu_rxd));
da3e3b87f8dd3d4 Sean Wang 2021-01-28 154
da3e3b87f8dd3d4 Sean Wang 2021-01-28 155 res = (struct mt7921_mcu_eeprom_info *)skb->data;
da3e3b87f8dd3d4 Sean Wang 2021-01-28 156
da3e3b87f8dd3d4 Sean Wang 2021-01-28 157 return 0;
da3e3b87f8dd3d4 Sean Wang 2021-01-28 158 }
da3e3b87f8dd3d4 Sean Wang 2021-01-28 159
:::::: The code at line 148 was first introduced by commit
:::::: da3e3b87f8dd3d44e83c7ab744bd1ad6ab9f8468 UPSTREAM: mt76: mt7921: add MCU support
:::::: TO: Sean Wang <sean.wang@mediatek.com>
:::::: CC: Commit Bot <commit-bot@chromium.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-13 16: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=202304140025.JDd41CCB-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.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.