10:04 a.m.
Hi Linus,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 291009f656e8eaebbdfd3a8d99f6b190a9ce9deb
commit: e1c6edcbea13de025c3406645b4cce4ac3baf973 leds: rt8515: Add Richtek RT8515 LED
driver
date: 12 days ago
config: i386-randconfig-a005-20210209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
#
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit...
git remote add linus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout e1c6edcbea13de025c3406645b4cce4ac3baf973
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
ld: drivers/leds/flash/leds-rt8515.o: in function `rt8515_v4l2_flash_release':
> drivers/leds/flash/leds-rt8515.c:216: undefined reference to
`v4l2_flash_release'
ld: drivers/leds/flash/leds-rt8515.o: in function
`rt8515_probe':
drivers/leds/flash/leds-rt8515.c:354: undefined reference to `v4l2_flash_init'
vim +216 drivers/leds/flash/leds-rt8515.c
213
214 static void rt8515_v4l2_flash_release(struct rt8515 *rt)
215 {
216 v4l2_flash_release(rt->v4l2_flash);
217 }
218
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
11:38 p.m.
I need Arnds help with this...
On Fri, Feb 12, 2021 at 12:05 AM kernel test robot <lkp(a)intel.com> wrote:
ld: drivers/leds/flash/leds-rt8515.o: in function
`rt8515_v4l2_flash_release':
>> drivers/leds/flash/leds-rt8515.c:216: undefined reference to
`v4l2_flash_release'
ld: drivers/leds/flash/leds-rt8515.o: in function `rt8515_probe':
drivers/leds/flash/leds-rt8515.c:354: undefined reference to `v4l2_flash_init'
So the problem is that this is compiled in, so CONFIG_LEDS_RT8515=y
(it is tristate so can also be a module)
but it depends on symbols from a module:
CONFIG_V4L2_FLASH_LED_CLASS=m.
In the code I try to only support the V4L2 interface when using V4L2:
#if IS_ENABLED(CONFIG_V4L2_FLASH_LED_CLASS)
(... V4L2 code...)
Is there a way to define in Kconfig that if and only if you enable
this other module it has to follow the y or m that we use for this
driver?
Or do I simply have to bite the bullet, make it bool and
depend on CONFIG_V4L2_FLASH_LED_CLASS || !CONFIG_V4L2_FLASH_LED_CLASS
?
Yours,
Linus Walleij
12:32 a.m.
On Fri 2021-02-12 13:38:58, Linus Walleij wrote:
I need Arnds help with this...
On Fri, Feb 12, 2021 at 12:05 AM kernel test robot <lkp(a)intel.com> wrote:
> ld: drivers/leds/flash/leds-rt8515.o: in function
`rt8515_v4l2_flash_release':
> >> drivers/leds/flash/leds-rt8515.c:216: undefined reference to
`v4l2_flash_release'
> ld: drivers/leds/flash/leds-rt8515.o: in function `rt8515_probe':
> drivers/leds/flash/leds-rt8515.c:354: undefined reference to
`v4l2_flash_init'
So the problem is that this is compiled in, so CONFIG_LEDS_RT8515=y
(it is tristate so can also be a module)
but it depends on symbols from a module:
CONFIG_V4L2_FLASH_LED_CLASS=m.
In the code I try to only support the V4L2 interface when using V4L2:
#if IS_ENABLED(CONFIG_V4L2_FLASH_LED_CLASS)
(... V4L2 code...)
Is there a way to define in Kconfig that if and only if you enable
this other module it has to follow the y or m that we use for this
driver?
Or do I simply have to bite the bullet, make it bool and
depend on CONFIG_V4L2_FLASH_LED_CLASS || !CONFIG_V4L2_FLASH_LED_CLASS
?
Arnd already submitted patch for this one... depends is right, no need
to make it bool, I believe.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
585
days inactive
586
days old
2 comments
3 participants
participants (3)
-
kernel test robot -
Linus Walleij -
Pavel Machek