From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>, backports@vger.kernel.org
Subject: Re: CONFIG_WLAN getting disabled - copy-list usage
Date: Tue, 10 Nov 2015 13:05:51 +0100 [thread overview]
Message-ID: <1447157151.2421.8.camel@sipsolutions.net> (raw)
In-Reply-To: <5641DD38.4080806@broadcom.com>
On Tue, 2015-11-10 at 13:04 +0100, Arend van Spriel wrote:
> On 11/02/2015 01:36 PM, Johannes Berg wrote:
> > FYI, if anyone's using backports with a copy-list file that
> > restricts
> > the wifi drivers to their own, and is working against a recent tree
> > that includes the drivers/net/wireless/realtek/ move, then
> > CONFIG_WLAN
> > will end up getting disabled.
> >
> > To fix that for now modify your copy-list to include
> > drivers/net/wireless/realtek/Makefile (and that file only).
> >
> > Once Kconfig changes go in and the Makefile statement
> >
> > obj-$(CONFIG_WLAN) += realtek/
> >
> > changes to
> >
> > obj-$(CONFIG_WLAN_REALTEK) += realtek/
> >
> > (or similar) this issue will go away.
>
> Thanks. It worked for me. As Kalle intends to move more drivers into
> vendor subfolder, can we expect this will happen again. Can we fix up
> kconfig handling for this?
>
I asked Kalle and he's planning to also add per-vendor Kconfig, at
which point this will not be needed any more. Like ethernet has,
really.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2015-11-10 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 12:36 CONFIG_WLAN getting disabled - copy-list usage Johannes Berg
2015-11-10 12:04 ` Arend van Spriel
2015-11-10 12:05 ` Johannes Berg [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=1447157151.2421.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=backports@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.