From: Greg KH <gregkh@linuxfoundation.org>
To: Jerome Pouiller <Jerome.Pouiller@silabs.com>
Cc: zhong jiang <zhongjiang@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: wfx: fix an undefined reference error when CONFIG_MMC=m
Date: Fri, 11 Oct 2019 11:02:56 +0200 [thread overview]
Message-ID: <20191011090256.GC1076760@kroah.com> (raw)
In-Reply-To: <3864047.FfxYVOUlJ1@pc-42>
On Fri, Oct 11, 2019 at 08:40:08AM +0000, Jerome Pouiller wrote:
> On Friday 11 October 2019 06:26:16 CEST Greg KH wrote:
> > CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
> >
> >
> > On Fri, Oct 11, 2019 at 11:02:19AM +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/Kconfig | 3 ++-
> > > drivers/staging/wfx/Makefile | 5 +++--
> > > 2 files changed, 5 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/staging/wfx/Kconfig b/drivers/staging/wfx/Kconfig
> > > index 9b8a1c7..4d045513 100644
> > > --- a/drivers/staging/wfx/Kconfig
> > > +++ b/drivers/staging/wfx/Kconfig
> > > @@ -1,7 +1,8 @@
> > > config WFX
> > > tristate "Silicon Labs wireless chips WF200 and further"
> > > depends on MAC80211
> > > - depends on (SPI || MMC)
> > > + depends on SPI
> > > + select MMC
> >
> > How about:
> > depends on (SPI && MMC)
>
> I dislike to force user to enable both buses while only one of them is
> sufficient. I would prefer to keep current dependencies and to add
> #ifdef around problematic functions.
Yes, that's the better thing to do here overall.
zhong, can you work on that?
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-11 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 3:02 zhong jiang
2019-10-11 4:26 ` Greg KH
2019-10-11 6:20 ` zhong jiang
2019-10-11 8:40 ` Jerome Pouiller
2019-10-11 9:02 ` Greg KH [this message]
2019-10-11 14:48 ` zhong jiang
2019-10-11 15:51 ` zhong jiang
2019-10-11 15:55 ` Jerome Pouiller
2019-10-11 16:13 ` zhong jiang
2019-10-11 16:16 ` Greg KH
2019-10-11 16:24 ` 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=20191011090256.GC1076760@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jerome.Pouiller@silabs.com \
--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
Powered by JetHome