linux-kernel - Re: [PATCH RESEND v2] staging: wfx: fix an undefined reference error when CONFIG

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]

Message-ID: <5DA13F17.6090409@huawei.com>
Date:   Sat, 12 Oct 2019 10:48:55 +0800
From:   zhong jiang <zhongjiang@...wei.com>
To:     Jerome Pouiller <Jerome.Pouiller@...abs.com>
CC:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND v2] staging: wfx: fix an undefined reference error
 when CONFIG_MMC=m

On 2019/10/12 0:57, Jerome Pouiller wrote:
> On Friday 11 October 2019 18:38:17 CEST zhong jiang wrote:
>> I hit the following error when compile the kernel.
>>
>> drivers/staging/wfx/main.o: In function `wfx_core_init':
>> /home/z00352263/linux-next/linux-next/drivers/staging/wfx/main.c:488: undefined reference to `sdio_register_driver'
>> drivers/staging/wfx/main.o: In function `wfx_core_exit':
>> /home/z00352263/linux-next/linux-next/drivers/staging/wfx/main.c:496: undefined reference to `sdio_unregister_driver'
>> drivers/staging/wfx/main.o:(.debug_addr+0x1a8): undefined reference to `sdio_register_driver'
>> drivers/staging/wfx/main.o:(.debug_addr+0x6f0): undefined reference to `sdio_unregister_driver'
> For information, I cannot reproduce your issue (it does not mean that
> the issue does not exist). In add, if you obtain undefined references,
> it should only happen when CONFIG_MMC is not defined.
I attach the config,  you can test it and reproduce the issue.

Thanks,
zhogn jiang
> Can you check that your Modules.symvers is up-to-date (by running a
> 'make modules') ?
>
>


View attachment "config.txt" of type "text/plain" (140907 bytes)