From: kernel test robot <lkp@intel.com>
To: Heiko Stuebner <heiko@sntech.de>, lee@kernel.org, srini@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, heiko@sntech.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] nvmem: Add driver for the eeprom in qnap-mcu controllers
Date: Mon, 3 Nov 2025 19:36:57 +0800 [thread overview]
Message-ID: <202511031906.3aAxVbZO-lkp@intel.com> (raw)
In-Reply-To: <20251102163955.294427-2-heiko@sntech.de>
Hi Heiko,
kernel test robot noticed the following build errors:
[auto build test ERROR on lee-leds/for-leds-next]
[also build test ERROR on lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes linus/master v6.18-rc4 next-20251103]
[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/Heiko-Stuebner/nvmem-Add-driver-for-the-eeprom-in-qnap-mcu-controllers/20251103-004523
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link: https://lore.kernel.org/r/20251102163955.294427-2-heiko%40sntech.de
patch subject: [PATCH v3 1/2] nvmem: Add driver for the eeprom in qnap-mcu controllers
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20251103/202511031906.3aAxVbZO-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251103/202511031906.3aAxVbZO-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/202511031906.3aAxVbZO-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/nvmem/qnap-mcu-eeprom.c: In function 'qnap_mcu_eeprom_read_block':
>> drivers/nvmem/qnap-mcu-eeprom.c:28:17: error: implicit declaration of function 'kzalloc' [-Wimplicit-function-declaration]
28 | reply = kzalloc(bytes + sizeof(cmd), GFP_KERNEL);
| ^~~~~~~
>> drivers/nvmem/qnap-mcu-eeprom.c:28:15: error: assignment to 'u8 *' {aka 'unsigned char *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
28 | reply = kzalloc(bytes + sizeof(cmd), GFP_KERNEL);
| ^
>> drivers/nvmem/qnap-mcu-eeprom.c:45:9: error: implicit declaration of function 'kfree' [-Wimplicit-function-declaration]
45 | kfree(reply);
| ^~~~~
vim +/kzalloc +28 drivers/nvmem/qnap-mcu-eeprom.c
20
21 static int qnap_mcu_eeprom_read_block(struct qnap_mcu *mcu, unsigned int offset,
22 void *val, size_t bytes)
23 {
24 const u8 cmd[] = { 0xf7, 0xa1, offset, bytes };
25 u8 *reply;
26 int ret = 0;
27
> 28 reply = kzalloc(bytes + sizeof(cmd), GFP_KERNEL);
29 if (!reply)
30 return -ENOMEM;
31
32 ret = qnap_mcu_exec(mcu, cmd, sizeof(cmd), reply, bytes + sizeof(cmd));
33 if (ret)
34 goto out;
35
36 /* First bytes must mirror the sent command */
37 if (memcmp(cmd, reply, sizeof(cmd))) {
38 ret = -EIO;
39 goto out;
40 }
41
42 memcpy(val, reply + sizeof(cmd), bytes);
43
44 out:
> 45 kfree(reply);
46 return ret;
47 }
48
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-03 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 16:39 [PATCH v3 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Heiko Stuebner
2025-11-02 16:39 ` [PATCH v3 1/2] nvmem: Add driver for the eeprom in qnap-mcu controllers Heiko Stuebner
2025-11-03 11:36 ` kernel test robot [this message]
2025-11-03 23:00 ` kernel test robot
2025-11-02 16:39 ` [PATCH v3 2/2] mfd: qnap-mcu: Hook up the eeprom sub-device Heiko Stuebner
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=202511031906.3aAxVbZO-lkp@intel.com \
--to=lkp@intel.com \
--cc=heiko@sntech.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=srini@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