From: Dan Carpenter <error27@gmail.com>
To: oe-kbuild@lists.linux.dev, Felix Fietkau <nbd@nbd.name>
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: drivers/net/ethernet/mediatek/mtk_wed_debugfs.c:73 dump_wed_regs() error: uninitialized symbol 'val'.
Date: Mon, 12 Dec 2022 10:18:01 +0300 [thread overview]
Message-ID: <202212110120.ZqvaZrGs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3ecc37918c80ffdbfa8f08d3e75a0a9fca1c1979
commit: 804775dfc2885e93a0a4b35db1914c2cc25172b5 net: ethernet: mtk_eth_soc: add support for Wireless Ethernet Dispatch (WED)
config: openrisc-randconfig-m031-20221210
compiler: or1k-linux-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
smatch warnings:
drivers/net/ethernet/mediatek/mtk_wed_debugfs.c:73 dump_wed_regs() error: uninitialized symbol 'val'.
vim +/val +73 drivers/net/ethernet/mediatek/mtk_wed_debugfs.c
804775dfc2885e Felix Fietkau 2022-04-05 46 static void
804775dfc2885e Felix Fietkau 2022-04-05 47 dump_wed_regs(struct seq_file *s, struct mtk_wed_device *dev,
804775dfc2885e Felix Fietkau 2022-04-05 48 const struct reg_dump *regs, int n_regs)
804775dfc2885e Felix Fietkau 2022-04-05 49 {
804775dfc2885e Felix Fietkau 2022-04-05 50 const struct reg_dump *cur;
804775dfc2885e Felix Fietkau 2022-04-05 51 u32 val;
804775dfc2885e Felix Fietkau 2022-04-05 52
804775dfc2885e Felix Fietkau 2022-04-05 53 for (cur = regs; cur < ®s[n_regs]; cur++) {
804775dfc2885e Felix Fietkau 2022-04-05 54 switch (cur->type) {
804775dfc2885e Felix Fietkau 2022-04-05 55 case DUMP_TYPE_STRING:
804775dfc2885e Felix Fietkau 2022-04-05 56 seq_printf(s, "%s======== %s:\n",
804775dfc2885e Felix Fietkau 2022-04-05 57 cur > regs ? "\n" : "",
804775dfc2885e Felix Fietkau 2022-04-05 58 cur->name);
804775dfc2885e Felix Fietkau 2022-04-05 59 continue;
804775dfc2885e Felix Fietkau 2022-04-05 60 case DUMP_TYPE_WED:
804775dfc2885e Felix Fietkau 2022-04-05 61 val = wed_r32(dev, cur->offset);
804775dfc2885e Felix Fietkau 2022-04-05 62 break;
804775dfc2885e Felix Fietkau 2022-04-05 63 case DUMP_TYPE_WDMA:
804775dfc2885e Felix Fietkau 2022-04-05 64 val = wdma_r32(dev, cur->offset);
804775dfc2885e Felix Fietkau 2022-04-05 65 break;
804775dfc2885e Felix Fietkau 2022-04-05 66 case DUMP_TYPE_WPDMA_TX:
804775dfc2885e Felix Fietkau 2022-04-05 67 val = wpdma_tx_r32(dev, cur->base, cur->offset);
804775dfc2885e Felix Fietkau 2022-04-05 68 break;
804775dfc2885e Felix Fietkau 2022-04-05 69 case DUMP_TYPE_WPDMA_TXFREE:
804775dfc2885e Felix Fietkau 2022-04-05 70 val = wpdma_txfree_r32(dev, cur->offset);
804775dfc2885e Felix Fietkau 2022-04-05 71 break;
There are no DUMP_TYPE_WPDMA_RX and DUMP_TYPE_WED_RRO cases or a default
case.
804775dfc2885e Felix Fietkau 2022-04-05 72 }
804775dfc2885e Felix Fietkau 2022-04-05 @73 print_reg_val(s, cur->name, val);
804775dfc2885e Felix Fietkau 2022-04-05 74 }
804775dfc2885e Felix Fietkau 2022-04-05 75 }
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-12-12 7:18 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=202212110120.ZqvaZrGs-lkp@intel.com \
--to=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nbd@nbd.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®