From: Mattias Nissler <mattias.nissler@gmx.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Adrian Bunk <bunk@stusta.de>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: RFC: always enable MAC80211_RC_PID?
Date: Thu, 26 Jun 2008 19:55:42 +0200 [thread overview]
Message-ID: <1214502942.4432.6.camel@localhost> (raw)
In-Reply-To: <20080624124311.GC16021@cs181140183.pp.htv.fi>
Just what I remember about the discussion that led to the ugly Makefile.
On Tue, 2008-06-24 at 15:43 +0300, Adrian Bunk wrote:
>
> Can we get one of either:
> - all selected mac80211 algorithms are built into the mac80211 module or
IIRC, this was originally voted against because this approach would
increase kernel image size or module size unnecessarily.
> - all selected mac80211 algorithms (including the default one) are in
> their own modules
The argument against this was that there are people who don't compile in
module autoloading, can't figure out what's wrong (in spite of the
syslog message) and complain about wireless not working...
Anyway, I always liked any of the two things you suggested better than
what we have now.
Mattias
next prev parent reply other threads:[~2008-06-26 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 12:55 RFC: always enable MAC80211_RC_PID? Adrian Bunk
2008-06-22 15:04 ` Luis R. Rodriguez
2008-06-23 6:57 ` Kalle Valo
2008-06-24 9:04 ` Johannes Berg
2008-06-24 12:43 ` Adrian Bunk
2008-06-24 21:12 ` John W. Linville
2008-06-26 10:38 ` [2.6 patch] build algorithms into the mac80211 module Adrian Bunk
2008-06-26 13:46 ` Johannes Berg
2008-06-26 21:35 ` RFC: always enable MAC80211_RC_PID? Luis R. Rodriguez
2008-06-26 22:37 ` Tomas Winkler
2008-06-26 17:55 ` Mattias Nissler [this message]
2008-06-26 18:10 ` Adrian Bunk
2008-06-25 0:56 ` Nick Kossifidis
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=1214502942.4432.6.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=bunk@kernel.org \
--cc=bunk@stusta.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=netdev@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).