From: Jerome Pouiller <Jerome.Pouiller@silabs.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v2] staging: wfx: fix an undefined reference error when CONFIG_MMC=m
Date: Fri, 11 Oct 2019 16:57:28 +0000 [thread overview]
Message-ID: <8983882.YYcFGT5GfJ@pc-42> (raw)
In-Reply-To: <1570811647-64905-1-git-send-email-zhongjiang@huawei.com>
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.
Can you check that your Modules.symvers is up-to-date (by running a
'make modules') ?
--
Jérôme Pouiller
next prev parent reply other threads:[~2019-10-11 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 16:34 [PATCH RESEND v2] staging: wfx: fix an undefined reference error when CONFIG_MMC=m zhong jiang
2019-10-11 16:57 ` Jerome Pouiller [this message]
2019-10-12 2:48 ` zhong jiang
2019-10-14 9:53 ` Jerome Pouiller
2019-10-14 10:06 ` Jerome Pouiller
2019-10-14 11:19 ` gregkh
2019-10-14 15:30 ` zhong jiang
2019-10-17 3:54 ` zhong jiang
2019-10-11 17:03 ` Greg KH
2019-10-12 2:49 ` zhong jiang
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=8983882.YYcFGT5GfJ@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongjiang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).