From: <Eugen.Hristev@microchip.com>
To: <linux-media@vger.kernel.org>, <hverkuil-cisco@xs4all.nl>,
<arnd@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lkp@intel.com>
Subject: Re: [PATCH] media: atmel: fix build when ISC=m and XISC=y
Date: Mon, 26 Jul 2021 09:52:53 +0000 [thread overview]
Message-ID: <44a267f7-d01d-36de-0a14-0fa0eb14b6ea@microchip.com> (raw)
In-Reply-To: <20210705125708.121902-1-eugen.hristev@microchip.com>
On 7/5/21 3:57 PM, Eugen Hristev wrote:
> Building VIDEO_ATMEL_ISC as module and VIDEO_ATMEL_XISC as built-in
> (or viceversa) causes build errors:
>
> or1k-linux-ld: drivers/media/platform/atmel/atmel-isc-base.o: in function `isc_async_complete':
> atmel-isc-base.c:(.text+0x40d0): undefined reference to `__this_module'
> or1k-linux-ld: atmel-isc-base.c:(.text+0x40f0): undefined reference to `__this_module'
> or1k-linux-ld: drivers/media/platform/atmel/atmel-isc-base.o:(.rodata+0x390): undefined reference to `__this_module'
> or1k-linux-ld: drivers/media/platform/atmel/atmel-isc-base.o:(__param+0x4): undefined reference to `__this_module'
> or1k-linux-ld: drivers/media/platform/atmel/atmel-isc-base.o:(__param+0x18): undefined reference to `__this_module'
>
> This is caused by the file atmel-isc-base.c which is common code between
> the two drivers.
>
> The solution is to create another Kconfig symbol that is automatically
> selected and generates the module atmel-isc-base.ko. This module can be
> loaded when both drivers are modules, or built-in when at least one of them
> is built-in.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: c9aa973884a1 ("media: atmel: atmel-isc: add microchip-xisc driver")
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
> ---
Hello Hans,
This build problem is causing plenty of robot reports and issues in
current 5.14 tree, also Arnd has sent a similar patch after mine was sent.
Could you have a look please such that we fix this for 5.14 ?
Thanks,
Eugen
prev parent reply other threads:[~2021-07-26 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 12:57 Eugen Hristev
2021-07-26 9:52 ` Eugen.Hristev [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=44a267f7-d01d-36de-0a14-0fa0eb14b6ea@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=arnd@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®