linux-kernel - Re: linux-next: build failure after merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 13 Mar 2020 07:48:07 +0100
From:   Marco Felsch <m.felsch@...gutronix.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Hans Verkuil <hverkuil-cisco@...all.nl>
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree

Hi Stephen,

On 20-03-13 13:19, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the v4l-dvb tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> ERROR: modpost: "fwnode_get_name" [drivers/media/v4l2-core/v4l2-fwnode.ko] undefined!
> 
> Caused by commit
> 
>   dfc22c073b78 ("media: v4l2-fwnode: add initial connector parsing support")
> 
> I have used the v4l-dvb tree from next-20200312 for today.

I'm sorry for that. I put my branch on our 0day to test most of the
compile configs. Obviously this casae wasn't covered..

@Sakari
I will send a patch to fix this by adding:
EXPORT_SYMBOL_GPL(fwnode_get_name).

Regards,
  Marco