From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] staging/wilc: fix Kconfig dependencies, second try
Date: Wed, 21 Oct 2015 00:42:23 +0200 [thread overview]
Message-ID: <4126905.7rHMRoCZhU@wuerfel> (raw)
In-Reply-To: <4095810.4Q9e8Lc4je@wuerfel>
On Monday 19 October 2015 11:53:40 Arnd Bergmann wrote:
> On Monday 19 October 2015 11:39:31 Arnd Bergmann wrote:
> > On Monday 19 October 2015 16:54:23 Tony Cho wrote:
> > > Hi Arnd Bergmann,
> > >
> > > When I apply this patch, I cannot make WILC1000 module (wilc1000.ko) because CONFIG_WILC1000 is y and also I can see some link errors for the cfg80211 APIs.
> > >
> > > Can you consider this patch?
> >
> > Ah, you are right. I see the same thing now and don't know what caused me
> > to send the patch in an incomplete state.
> >
> > I hope this snippet is the last missing piece:
> >
>
> No, that was not it either, I'll start over to think this through.
>
> The real solution of course is to make it possible to load both the
> SPI and MMC front-ends at the same time and have a common base driver,
> which I might have to do, in order to clear myself of the shame of sending
> not one but two incorrect fixes for this problem
I spent too much time on it now, but I have a series that should fix
this part for real and let you build both drivers into the kernel
(or as modules) in a single configuration.
Arnd
prev parent reply other threads:[~2015-10-20 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 20:45 [PATCH] staging/wilc: fix Kconfig dependencies, second try Arnd Bergmann
2015-10-19 7:54 ` Tony Cho
2015-10-19 9:39 ` Arnd Bergmann
2015-10-19 9:53 ` Arnd Bergmann
2015-10-20 22:42 ` Arnd Bergmann [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=4126905.7rHMRoCZhU@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).