Re: [ksinyuk:drm-tip 6/12] amdgpu_dm_connector_test.c:undefined reference to `parse_hdmi_amd_vsdb'

Mario Limonciello <[email protected]>
Newsgroups dev.linux.lists.oe-kbuild-all
Message-ID <[email protected]>
On 8/27/26 10:47 AM, Doug Anderson wrote:
> Hi,
> 
> On Thu, Aug 27, 2026 at 8:31 AM kernel test robot <[email protected]> wrote:
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ksinyuk/linux.git drm-tip
>> head:   e3e05bddbe9fea67639d2a3551e7cf2d473b804c
>> commit: 6fa42e05f7e63d41ade0e59fa5d94ca8028f7887 [6/12] Merge remote-tracking branch 'drm-misc/drm-misc-next' into drm-tip
>> config: um-allyesconfig (https://download.01.org/0day-ci/archive/20260827/[email protected]/config)
>> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260827/[email protected]/reproduce)
>>
>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <[email protected]>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
>>
>> All errors (new ones prefixed by >>):
>>
>>     /usr/bin/ld: drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.o: in function `dm_test_parse_hdmi_amd_vsdb_no_cea_ext':
>>>> amdgpu_dm_connector_test.c:(.text+0x8cfe): undefined reference to `parse_hdmi_amd_vsdb'
>>     /usr/bin/ld: drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.o: in function `dm_test_parse_hdmi_amd_vsdb_no_extensions':
>>     amdgpu_dm_connector_test.c:(.text+0x91c8): undefined reference to `parse_hdmi_amd_vsdb'
>>     /usr/bin/ld: drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_connector_test.o: in function `dm_test_parse_hdmi_amd_vsdb_null_edid':
>>     amdgpu_dm_connector_test.c:(.text+0x95ca): undefined reference to `parse_hdmi_amd_vsdb'
>>     /usr/lib/gcc/x86_64-linux-gnu/14/crtbegin.o: in function `deregister_tm_clones':
>>     crtstuff.c:(.text+0x7): relocation truncated to fit: R_X86_64_32S against `.tm_clone_table'
>>     /usr/lib/gcc/x86_64-linux-gnu/14/crtbegin.o: in function `register_tm_clones':
>>     crtstuff.c:(.text+0x38): relocation truncated to fit: R_X86_64_32S against `.tm_clone_table'
>>     collect2: error: ld returned 1 exit status
> 
> Not that this error seems to have anything to do with me, but I did a
> quick grep and my best guess is that the error you're seeing is
> related to this patch:
> 
> commit f65198b3d07389afdcb48e4ad00fea2aded95dfd
> Author:     Alex Huang <[email protected]>
> AuthorDate: Tue Aug 4 10:33:37 2026 -0400
> Commit:     Mario Limonciello <[email protected]>
> CommitDate: Mon Aug 10 23:26:00 2026 -0500
> 
>      drm/amd/display: Use HDMI FreeSync range from common EDID parser
> 
>      HDMI FreeSync on amdgpu is detected using the AMD VSDB parser in the
>      DMUB firmware, now that the common DRM EDID parser can do the same, use
>      the common parser.
> 
>      Extend get_amd_vsdb() to copy the relevant flags and data now being
>      extracted from the AMD VSDB. Additionally, parse_hdmi_amd_vsdb() and the
>      parse_edid_cea() firmware helpers now have no callers; remove them.
> 
>      Signed-off-by: Alex Huang <[email protected]>
>      Reviewed-by: Mario Limonciello (AMD) <[email protected]>
>      Link: https://patch.msgid.link/[email protected]
>      (Adjust for movement to amdgpu_dm_connector.c)
>      Signed-off-by: Mario Limonciello <[email protected]>
> 
> That seems to have removed the parse_hdmi_amd_vsdb(). Despite the
> commit message, the function prototype is still in a header and there
> are still callers to it in amdgpu_dm_connector_test.c.
> 
> Adding the two people involved in that patch to this email thread.
> 
> Seems like the kernel test robot could use some help identifying the
> proper patch / people involved.
> 
> -Doug

Alex (Deucher) is planning to send a PR after the merge window with the fix.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.