From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-media@vger.kernel.org,
Russell King <rmk+kernel@armlinux.org.uk>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Mar 26 (drivers/media/cec/i2c/tda9950)
Date: Thu, 27 Mar 2025 08:59:45 +0100 [thread overview]
Message-ID: <984e749e-e5d3-4985-aadc-703b803424f8@xs4all.nl> (raw)
In-Reply-To: <870f6a20-7edc-4115-a700-11c886f181cf@infradead.org>
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
prev parent reply other threads:[~2025-03-27 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 5:56 linux-next: Tree for Mar 26 Stephen Rothwell
2025-03-26 22:43 ` linux-next: Tree for Mar 26 (objtool: iommu) Randy Dunlap
2025-03-27 5:45 ` Josh Poimboeuf
2025-03-27 0:22 ` linux-next: Tree for Mar 26 (drivers/media/cec/i2c/tda9950) Randy Dunlap
2025-03-27 7:59 ` Hans Verkuil [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=984e749e-e5d3-4985-aadc-703b803424f8@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sfr@canb.auug.org.au \
/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®