From: kernel test robot <lkp@intel.com>
To: Markus Stockhausen <markus.stockhausen@gmx.de>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
chris.packham@alliedtelesis.co.nz
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Markus Stockhausen <markus.stockhausen@gmx.de>
Subject: Re: [PATCH v3 2/2] phy: Realtek Otto SerDes driver
Date: Wed, 16 Oct 2024 01:22:16 +0800 [thread overview]
Message-ID: <202410160149.TNGsZcue-lkp@intel.com> (raw)
In-Reply-To: <20241012134834.1306992-3-markus.stockhausen@gmx.de>
Hi Markus,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.12-rc3 next-20241015]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Markus-Stockhausen/dt-bindings-phy-add-realtek-rtl8380m-serdes/20241012-214949
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20241012134834.1306992-3-markus.stockhausen%40gmx.de
patch subject: [PATCH v3 2/2] phy: Realtek Otto SerDes driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241016/202410160149.TNGsZcue-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241016/202410160149.TNGsZcue-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/202410160149.TNGsZcue-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/phy/realtek/phy-rtk-otto-serdes.c:120:12: warning: format specifies type 'int' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
119 | dev_info(ctrl->dev, "firmware %s: loaded with %d bytes, %d sequences\n",
| ~~
| %zu
120 | fwname, ctrl->firmware->size, h->dirsize);
| ^~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:160:67: note: expanded from macro 'dev_info'
160 | dev_printk_index_wrap(_dev_info, KERN_INFO, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ~~~ ^~~~~~~~~~~
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) && MODULES [=y]
vim +120 drivers/phy/realtek/phy-rtk-otto-serdes.c
71
72 static int rtsds_fw_load(struct rtsds_ctrl *ctrl)
73 {
74 int ret;
75 struct rtsds_fw_head *h;
76 u32 checksum;
77 const char *msg;
78 const char *fwprop;
79 char fwname[128];
80
81 ret = device_property_read_string(ctrl->dev, "firmware-name", &fwprop);
82 if (ret)
83 snprintf(fwname, sizeof(fwname), "realtek/%s", ctrl->conf->fwname);
84 else if (strcmp(fwprop, ""))
85 snprintf(fwname, sizeof(fwname), "realtek/%s", fwprop);
86 else {
87 dev_info(ctrl->dev, "firmware deactivated, patching disabled\n");
88 return 0;
89 }
90
91 ret = firmware_request_nowarn(&ctrl->firmware, fwname, ctrl->dev);
92 if (ret < 0) {
93 msg = "not found";
94 goto error;
95 }
96
97 if (ctrl->firmware->size < 16) {
98 msg = "size to small";
99 goto error;
100 }
101
102 h = (struct rtsds_fw_head *)ctrl->firmware->data;
103 if (h->magic != RTSDS_FW_MAGIC) {
104 msg = "magic mismatch";
105 goto error;
106 }
107
108 if (h->filesize != ctrl->firmware->size) {
109 msg = "size mismatch";
110 goto error;
111 }
112
113 checksum = ~crc32(0xFFFFFFFFU, ctrl->firmware->data + 8, ctrl->firmware->size - 8);
114 if (h->checksum != checksum) {
115 msg = "checksum mismatch";
116 goto error;
117 }
118
119 dev_info(ctrl->dev, "firmware %s: loaded with %d bytes, %d sequences\n",
> 120 fwname, ctrl->firmware->size, h->dirsize);
121
122 return 0;
123 error:
124 dev_err(ctrl->dev, "firmware %s: %s, patching disabled\n", fwname, msg);
125 ctrl->firmware = NULL;
126 return -EINVAL;
127 }
128
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-15 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 13:48 [PATCH v3 0/2] phy: Realtek Otto SerDes: add new driver Markus Stockhausen
2024-10-12 13:48 ` [PATCH v3 1/2] dt-bindings: phy: add realtek,rtl8380m-serdes Markus Stockhausen
2024-10-14 7:18 ` Krzysztof Kozlowski
2024-10-14 10:59 ` AW: " markus.stockhausen
2024-10-12 13:48 ` [PATCH v3 2/2] phy: Realtek Otto SerDes driver Markus Stockhausen
2024-10-15 17:22 ` kernel test robot
2024-10-15 17:22 ` kernel test robot [this message]
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=202410160149.TNGsZcue-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=markus.stockhausen@gmx.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).