From: kernel test robot <lkp@intel.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [frank-w-bpi-r2-4.14:7.0-main 160/160] drivers/net/phy/as21xxx/as21xxx.c:645:27: warning: variable 'ret' set but not used
Date: Wed, 27 May 2026 01:50:29 +0800 [thread overview]
Message-ID: <202605270123.mnSYD1IM-lkp@intel.com> (raw)
tree: https://github.com/frank-w/BPI-R2-4.14 7.0-main
head: 1466910f17d99c182a9c3c92fe5d0a5ceb7c51a4
commit: a39b171ae20a66c1ecceb73ff1989db16fe54594 [160/160] net: phy: add as21xx downstream driver from 6.19 (1.9.1)
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20260527/202605270123.mnSYD1IM-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260527/202605270123.mnSYD1IM-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/202605270123.mnSYD1IM-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/phy/as21xxx/as21xxx.c: In function 'aeon_set_default_value':
>> drivers/net/phy/as21xxx/as21xxx.c:645:27: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
645 | int pos = 0, val, ret = 0, remaining;
| ^~~
vim +/ret +645 drivers/net/phy/as21xxx/as21xxx.c
637
638 static int aeon_set_default_value(struct phy_device *phydev)
639 {
640 static const unsigned char base_data[] = {0x32, 0x30, 0x32, 0x33, 0x30, 0x37, 0x31, 0x34};
641 unsigned char bytebuf[16];
642 unsigned short *wdata;
643 unsigned int mask;
644 int byte_count, wdata_count = 0;
> 645 int pos = 0, val, ret = 0, remaining;
646 unsigned char padded_bytes[MEM_WORD_SIZE] = {0};
647
648 mask = param1 | 14;
649 memcpy(bytebuf, base_data, sizeof(base_data));
650 bytebuf[8] = mask & 0xff;
651 bytebuf[9] = (mask >> 8) & 0xff;
652 byte_count = 10;
653
654 wdata = kmalloc(MAX_WDATA_SIZE * sizeof(unsigned short), GFP_KERNEL);
655 if (!wdata)
656 return -ENOMEM;
657
658 while (pos + MEM_WORD_SIZE <= byte_count) {
659 if (wdata_count + 2 > MAX_WDATA_SIZE) {
660 pr_err("wdata array overflow\n");
661 ret = -ENOSPC;
662 goto cleanup;
663 }
664 wdata[wdata_count++] = le16_to_cpu(*(unsigned short *)&bytebuf[pos]);
665 wdata[wdata_count++] = le16_to_cpu(*(unsigned short *)&bytebuf[pos + 2]);
666 pos += MEM_WORD_SIZE;
667 }
668
669 remaining = byte_count - pos;
670 if (remaining > 0) {
671 if (wdata_count + 2 <= MAX_WDATA_SIZE) {
672 // Here we just need padded_bytes once, otherwise we need to read from mem
673 memcpy(padded_bytes, &bytebuf[pos], remaining);
674 wdata[wdata_count++] = le16_to_cpu(*(unsigned short *)&padded_bytes[0]);
675 wdata[wdata_count++] = le16_to_cpu(*(unsigned short *)&padded_bytes[2]);
676 }
677 }
678
679 val = phy_read_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_CPU_CTRL); //GLB_REG_CPU_CTRL
680 val |= 0x12;
681 phy_write_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_CPU_CTRL, val);
682 phy_write_mmd(phydev, MDIO_MMD_VEND1, VEND1_FW_START_ADDR,
683 (u16)(AEON_MEM_DEFAULT_ADDR & 0xFFFF));
684 phy_modify_mmd(phydev, MDIO_MMD_VEND1,
685 VEND1_GLB_REG_MDIO_INDIRECT_ADDRCMD,
686 0x3ffc, 0xc000);
687 aeon_cl45_write_burst(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_MDIO_INDIRECT_LOAD,
688 (unsigned char *)wdata, wdata_count*2);
689 val = phy_read_mmd(phydev, MDIO_MMD_VEND1,
690 VEND1_GLB_REG_MDIO_INDIRECT_ADDRCMD); //GLB_REG_MDIO_INDIRECT_ADDRCMD
691 val &= 0x3FFF;
692 phy_write_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_MDIO_INDIRECT_ADDRCMD, val);
693 val = phy_read_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_CPU_CTRL); //GLB_REG_CPU_CTRL
694 val &= 0xFFED;
695 phy_write_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLB_REG_CPU_CTRL, val);
696
697 cleanup:
698 kfree(wdata);
699 return 0;
700 }
701
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-26 17:51 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=202605270123.mnSYD1IM-lkp@intel.com \
--to=lkp@intel.com \
--cc=frank-w@public-files.de \
--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.