From: zhong jiang <zhongjiang@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <Jerome.Pouiller@silabs.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v2] staging: wfx: fix an undefined reference error when CONFIG_MMC=m
Date: Sat, 12 Oct 2019 10:49:44 +0800 [thread overview]
Message-ID: <5DA13F48.4010406@huawei.com> (raw)
In-Reply-To: <20191011170331.GA1296994@kroah.com>
On 2019/10/12 1:03, Greg KH wrote:
> On Sat, Oct 12, 2019 at 12:34:07AM +0800, 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'
>>
>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>> ---
>> drivers/staging/wfx/Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
> What changed from v1? Always put that below the --- line.
>
> v3 please?
Fine, I will repost in v3. Thanks,
Sincerely,
zhong jiang
> thanks,
>
> greg k-h
>
> .
>
prev parent reply other threads:[~2019-10-12 2:49 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
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 [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=5DA13F48.4010406@huawei.com \
--to=zhongjiang@huawei.com \
--cc=Jerome.Pouiller@silabs.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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).