On Sep 16, 7:17am, Masao Uebayashi wrote:
}
} I thought module names alway match what's "define"'ed in config(1) files...
At this time, config(1) has absolutely nothing to do with
modules. There is a movement afoot to change that. I'll just say that
I don't agree with changing that, but I
Yes, wlan was my first choice, cimply because that is the name of the
config attribute.
But it seems a consensus is emerging that the module name should be
"net80211" so that's what I'm going to do (assuming I figure out the
link_set issue).
I'll leave the rototilling of the config files for
I thought module names alway match what's "define"'ed in config(1) files...
... and now I've found it's "wlan", which should be changed to a saner
name like "net80211".
On Thu, Apr 26, 2012 at 9:52 AM, Paul Goyette wrote:
> I'm in the process of modularizing the ieee80211 (Wireless LAN) code, an
In article <20120426013452.gl20...@pixotech.com>,
David Young wrote:
>On Wed, Apr 25, 2012 at 05:52:31PM -0700, Paul Goyette wrote:
>> I'm in the process of modularizing the ieee80211 (Wireless LAN)
>> code, and would like some feedback on what the module's name should
>> be. I can think of at l
On Wed, Apr 25, 2012 at 05:52:31PM -0700, Paul Goyette wrote:
> I'm in the process of modularizing the ieee80211 (Wireless LAN)
> code, and would like some feedback on what the module's name should
> be. I can think of at least three or four likely candidates:
>
> net80211
> ieee80211
I'm in the process of modularizing the ieee80211 (Wireless LAN) code,
and would like some feedback on what the module's name should be. I can
think of at least three or four likely candidates:
net80211
ieee80211
wlan
wireless-lan
I'm leaning towards the simples
