From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [2.6 patch] build algorithms into the mac80211 module
Date: Thu, 26 Jun 2008 15:46:15 +0200 [thread overview]
Message-ID: <1214487975.20763.46.camel@johannes.berg> (raw)
In-Reply-To: <20080626103813.GB30359@cs181140183.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Thu, 2008-06-26 at 13:38 +0300, Adrian Bunk wrote:
> On Tue, Jun 24, 2008 at 05:12:22PM -0400, John W. Linville wrote:
> > On Tue, Jun 24, 2008 at 03:43:14PM +0300, Adrian Bunk wrote:
> >
> > > Can we get one of either:
> > > - all selected mac80211 algorithms are built into the mac80211 module or
> >
> > This seems fine to me.
> >
> > > - all selected mac80211 algorithms (including the default one) are in
> > > their own modules
> >
> > We got here trying to avoid this one in the first place.
>
> What about the patch below?
Seems ok to me, especially since we don't have a tunable for the rate
control algorithm nor any other than the iwlwifi ones and this one...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-06-26 13:46 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 [this message]
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
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=1214487975.20763.46.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=bunk@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).