linux-kernel - Re: linux-next: Tree for Mar 26 (drivers/media/cec/i2c/tda9950)

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] [day] [month] [year] [list]

Message-ID: <984e749e-e5d3-4985-aadc-703b803424f8@xs4all.nl>
Date: Thu, 27 Mar 2025 08:59:45 +0100
From: Hans Verkuil <hverkuil-cisco@...all.nl>
To: Randy Dunlap <rdunlap@...radead.org>,
 Stephen Rothwell <sfr@...b.auug.org.au>,
 Linux Next Mailing List <linux-next@...r.kernel.org>,
 Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 linux-media@...r.kernel.org, Russell King <rmk+kernel@...linux.org.uk>,
 "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: Tree for Mar 26 (drivers/media/cec/i2c/tda9950)

On 27/03/2025 01:22, Randy Dunlap wrote:
> 
> 
> On 3/25/25 10:56 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20250325:
>>
> 
> on x86_64, when CONFIG_I2C=m and
> CONFIG_CEC_NXP_TDA9950=y:
> 
> ld: vmlinux.o: in function `tda9950_write_range':
> tda9950.c:(.text+0x1225126): undefined reference to `i2c_transfer'
> ld: vmlinux.o: in function `tda9950_read':
> tda9950.c:(.text+0x122553f): undefined reference to `i2c_transfer'
> ld: vmlinux.o: in function `tda9950_irq':
> tda9950.c:(.text+0x122573e): undefined reference to `i2c_transfer'
> ld: vmlinux.o: in function `tda9950_driver_init':
> tda9950.c:(.init.text+0x726a3): undefined reference to `i2c_register_driver'
> ld: vmlinux.o: in function `tda9950_driver_exit':
> tda9950.c:(.exit.text+0x54fc): undefined reference to `i2c_del_driver'
> 
> 

Dmitry, two patches were posted fixing this (both effectively identical):

https://patchwork.linuxtv.org/project/linux-media/patch/20250227140301.3062217-1-arnd@kernel.org/
https://patchwork.linuxtv.org/project/linux-media/patch/20250322024914.3622546-1-yuehaibing@huawei.com/

I suspect neither of these was picked up by the drm folks? Since the move of this tda9950
driver from the drm subsystem to the media subsystem went through the drm tree, I can't apply the fix.

Once rc1 is released I can take care of it myself, since then it is part of the media subsystem.

Regards,

	Hans