The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "kernel test robot" <lkp@intel.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
Subject: Re: [PATCH] nvmem: layouts: Add fixed-layout driver
Date: Mon, 11 May 2026 17:09:25 +0200	[thread overview]
Message-ID: <DIFXY1KVLFNQ.37A8E2MRLMIYI@bootlin.com> (raw)
In-Reply-To: <202605112100.08bk8fTf-lkp@intel.com>

On Mon May 11, 2026 at 3:06 PM CEST, kernel test robot wrote:
> 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: sh-defconfig (https://download.01.org/0day-ci/archive/20260511/202605112100.08bk8fTf-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/20260511/202605112100.08bk8fTf-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/202605112100.08bk8fTf-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>    sh4-linux-ld: drivers/nvmem/layouts/fixed-layout.o: in function `fixed_layout_layout_init':
>>> fixed-layout.c:(.init.text+0x18): undefined reference to `__nvmem_layout_driver_register'
>    sh4-linux-ld: drivers/nvmem/layouts/fixed-layout.o: in function `fixed_layout_layout_exit':
>>> fixed-layout.c:(.exit.text+0x14): undefined reference to `nvmem_layout_driver_unregister'

I confirm this is an issue. I will make sure this is fixed in v2.

My current plan is to modify drivers/nvmem/layouts/Makefile:
-obj-y += fixed-layout.o
+obj-$(CONFIG_NVMEM_LAYOUTS) += fixed-layout.o

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2026-05-11 15:09 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 [this message]
2026-05-11 13:43 ` kernel test robot
2026-05-11 15:04 ` kernel test robot

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=DIFXY1KVLFNQ.37A8E2MRLMIYI@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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