From: kernel test robot <lkp@intel.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Srinivas Kandagatla <srini@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org,
"Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
Subject: Re: [PATCH] nvmem: layouts: Add fixed-layout driver
Date: Mon, 11 May 2026 17:04:38 +0200 [thread overview]
Message-ID: <202605111648.gLUTeOnR-lkp@intel.com> (raw)
In-Reply-To: <20260505-mathieu-nvmem-fixed-layout-v1-1-7f6ecbce108d@bootlin.com>
Hi Mathieu,
kernel test robot noticed the following build errors:
[auto build test ERROR on 7fd2df204f342fc17d1a0bfcd474b24232fb0f32]
url: https://github.com/intel-lab-lkp/linux/commits/Mathieu-Dubois-Briand/nvmem-layouts-Add-fixed-layout-driver/20260511-170834
base: 7fd2df204f342fc17d1a0bfcd474b24232fb0f32
patch link: https://lore.kernel.org/r/20260505-mathieu-nvmem-fixed-layout-v1-1-7f6ecbce108d%40bootlin.com
patch subject: [PATCH] nvmem: layouts: Add fixed-layout driver
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260511/202605111648.gLUTeOnR-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260511/202605111648.gLUTeOnR-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/202605111648.gLUTeOnR-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/nvmem/layouts/fixed-layout.o: in function `fixed_layout_layout_init':
>> drivers/nvmem/layouts/fixed-layout.c:47:(.init.text+0x10): undefined reference to `__nvmem_layout_driver_register'
ld: drivers/nvmem/layouts/fixed-layout.o: in function `fixed_layout_layout_exit':
>> drivers/nvmem/layouts/fixed-layout.c:47:(.exit.text+0x9): undefined reference to `nvmem_layout_driver_unregister'
vim +47 drivers/nvmem/layouts/fixed-layout.c
38
39 static struct nvmem_layout_driver fixed_layout_layout = {
40 .driver = {
41 .name = "fixed-layout",
42 .of_match_table = fixed_layout_of_match_table,
43 },
44 .probe = fixed_layout_probe,
45 .remove = fixed_layout_remove,
46 };
> 47 module_nvmem_layout_driver(fixed_layout_layout);
48
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-11 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 8:42 [PATCH] nvmem: layouts: Add fixed-layout driver Mathieu Dubois-Briand
2026-05-05 9:14 ` Miquel Raynal
2026-05-05 12:58 ` Mathieu Dubois-Briand
2026-05-05 13:15 ` Miquel Raynal
2026-05-11 13:06 ` kernel test robot
2026-05-11 15:09 ` Mathieu Dubois-Briand
2026-05-11 13:43 ` kernel test robot
2026-05-11 15:04 ` 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=202605111648.gLUTeOnR-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=srini@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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