From: Miquel Raynal <miquel.raynal@bootlin.com>
To: <markus.stockhausen@gmx.de>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"'kernel test robot'" <lkp@intel.com>
Subject: Re: AW: drivers/mtd/nand/ecc-realtek.c:443:undefined reference to `dma_free_pages'
Date: Wed, 19 Nov 2025 20:27:33 +0100 [thread overview]
Message-ID: <875xb53jru.fsf@bootlin.com> (raw)
In-Reply-To: <003801dc4fd1$a76efc20$f64cf460$@gmx.de> (markus stockhausen's message of "Fri, 7 Nov 2025 11:31:18 +0100")
Hi Markus,
On 07/11/2025 at 11:31:18 +01, <markus.stockhausen@gmx.de> wrote:
>> Von: kernel test robot <lkp@intel.com>
>> Gesendet: Freitag, 7. November 2025 04:39
>> An: Markus Stockhausen <markus.stockhausen@gmx.de>
>> Cc: oe-kbuild-all@lists.linux.dev; linux-kernel@vger.kernel.org; Miquel
> Raynal <miquel.raynal@bootlin.com>
>> Betreff: drivers/mtd/nand/ecc-realtek.c:443:undefined reference to
> `dma_free_pages'
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
>> head: 4a0c9b3391999818e2c5b93719699b255be1f682
>> commit: 3148d0e5b1c5733d69ec51b70c8280e46488750a mtd: nand: realtek-ecc:
> Add Realtek external ECC engine support
>> date: 6 weeks ago
>> config: sh-randconfig-r121-20251107
> (https://download.01.org/0day-ci/archive/20251107/202511071114.8WeW2GZK-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/20251107/202511071114.8WeW2GZK-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/202511071114.8WeW2GZK-lkp@intel.
>> | com/
>>
>> All errors (new ones prefixed by >>):
>>
>> sh4-linux-ld: drivers/mtd/nand/ecc-realtek.o: in function
> `rtl_ecc_remove':
>> >> drivers/mtd/nand/ecc-realtek.c:443:(.text+0x1f8): undefined reference
> to `dma_free_pages'
>> sh4-linux-ld: drivers/mtd/nand/ecc-realtek.o: in function
> `rtl_ecc_probe':
>> >> drivers/mtd/nand/ecc-realtek.c:434:(.text+0x2e8): undefined reference
> to `dma_alloc_pages'
>> sh4-linux-ld: drivers/media/i2c/tc358746.o: in function
> `tc358746_probe':
>> drivers/media/i2c/tc358746.c:1585:(.text+0x15cc): undefined reference
> to `devm_clk_hw_register'
>> sh4-linux-ld: drivers/media/i2c/tc358746.c:1610:(.text+0x163c):
> undefined reference to `devm_of_clk_add_hw_provider'
>> sh4-linux-ld: drivers/media/i2c/tc358746.c:1610:(.text+0x1640):
> undefined reference to `of_clk_hw_simple_get'
>
> Hi Miquel,
>
> help. What needs to be done here?
>
> Markus
Looks like the sh architecture has no DMA support whereas the driver
depends on it without properly advertising it in Kconfig. The driver may
be enabled on this architecture due to COMPILE_TEST being set in
Kconfig.
I'll send a small fix.
Cheers,
Miquèl
prev parent reply other threads:[~2025-11-19 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:39 drivers/mtd/nand/ecc-realtek.c:443:undefined reference to `dma_free_pages' kernel test robot
2025-11-07 10:31 ` AW: " markus.stockhausen
2025-11-19 19:27 ` Miquel Raynal [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=875xb53jru.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=markus.stockhausen@gmx.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.