Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Subversion Log


Commit Date  
[r4182] (HEAD) by proski

Remove __devinitdata, it's obsolete now

2013-03-06 15:53:15 Tree
[r4181] by proski

Remove __devinitdata, it's obsolete now

2013-03-06 15:52:20 Tree
[r4180] by proski

Use "%s" in err() calls to fix a warning on Ubuntu 10.04

err() would be confused if the interface name has formatting characters.

2012-05-01 19:55:40 Tree
[r4179] by proski

Use "%s" in err() calls to fix a warning on Ubuntu 10.04

err() would be confused if the interface name has formatting characters.

2012-05-01 19:52:26 Tree
[r4178] by proski

Don't reference vlan_group without IEEE80211_VLAN_TAG_USED set

struct vlan_group will be removed in Linux 3.3.

2012-01-30 19:56:17 Tree
[r4177] by proski

Don't reference vlan_group without IEEE80211_VLAN_TAG_USED set

struct vlan_group will be removed in Linux 3.3.

2012-01-30 19:55:03 Tree
[r4176] by proski

Use ndo_set_rx_mode instead of ndo_set_multicast_list on Linux 3.2+

2011-11-22 17:30:17 Tree
[r4175] by proski

Use ndo_set_rx_mode instead of ndo_set_multicast_list on Linux 3.2+

2011-11-22 17:22:34 Tree
[r4174] by proski

Merge 4149:4172 from trunk

2011-10-25 21:38:00 Tree
[r4173] by proski

Remove -Werror from WARNINGS

It's impossible to eliminate all warnings with all combinations of
kernels and compilers. Users are punished for using untested
combinations that should be OK. Other projects don't use -Werror and
nothing bad happens.

Future compilers would surely introduce new warnings. MadWifi doesn't
need to break because of that.

There is no way to make -Werror apply to MadWifi code but not to the
kernel headers. Linux kernel doesn't use -Werror, why should MadWifi?

Using -Werror creates a false sense of security. It's easy to assume
that the code is warning-free at least on the developers' systems.
However, broken code was committed in the past that would not compile at
all. Code quality means more that absence of warnings. It cannot be
ensured by -Werror.

2011-10-07 21:43:03 Tree
[r4172] by proski

Remove -Werror from WARNINGS

It's impossible to eliminate all warnings with all combinations of
kernels and compilers. Users are punished for using untested
combinations that should be OK. Other projects don't use -Werror and
nothing bad happens.

Future compilers would surely introduce new warnings. MadWifi doesn't
need to break because of that.

There is no way to make -Werror apply to MadWifi code but not to the
kernel headers. Linux kernel doesn't use -Werror, why should MadWifi?

Using -Werror creates a false sense of security. It's easy to assume
that the code is warning-free at least on the developers' systems.
However, broken code was committed in the past that would not compile at
all. Code quality means more that absence of warnings. It cannot be
ensured by -Werror.

2011-10-07 21:42:25 Tree
[r4171] by proski

Eliminate ATH_GET_NETDEV_DEV, it breaks on some CentOS kernels

Instead, use sc->sc_bdev to find the physical device. sc->sc_bdev is
NULL on AHB and we don't use SET_NETDEV_DEV on AHB anyway, so do it on
PCI only.

2011-10-07 21:31:51 Tree
[r4170] by proski

Eliminate ATH_GET_NETDEV_DEV, it breaks on some CentOS kernels

Instead, use sc->sc_bdev to find the physical device. sc->sc_bdev is
NULL on AHB and we don't use SET_NETDEV_DEV on AHB anyway, so do it on
PCI only.

2011-10-07 21:30:59 Tree
[r4169] by proski

Don't redefine netdev_for_each_mc_addr()

It's already defined in CentOS 2.6.18-238.19.1.el5 kernel. Use
parentheses around dev to be safer.

2011-10-07 21:16:17 Tree
[r4168] by proski

Don't redefine netdev_for_each_mc_addr()

It's already defined in CentOS 2.6.18-238.19.1.el5 kernel. Use
parentheses around dev to be safer.

2011-10-07 21:14:47 Tree
[r4167] by proski

Fix typos found by codespell

2011-08-26 15:38:40 Tree
[r4166] by proski

Fix typos found by codespell

2011-08-26 15:31:01 Tree
[r4165] by proski

Fix compilation on Linux 3.1 broken by VLAN API changes

Don't define IEEE80211_VLAN_TAG_USED on Linux 3.1 and newer. Don't use
vlan_hwaccel_rx() if IEEE80211_VLAN_TAG_USED is not 1.

2011-08-15 19:10:12 Tree
[r4164] by proski

Fix compilation with IEEE80211_DEBUG_REFCNT=1

2011-08-15 18:59:53 Tree
[r4163] by proski

Fix compilation on Linux 3.1 broken by VLAN API changes

Don't define IEEE80211_VLAN_TAG_USED on Linux 3.1 and newer. Don't use
vlan_hwaccel_rx() if IEEE80211_VLAN_TAG_USED is not 1.

2011-08-15 18:59:22 Tree
[r4162] by proski

Don't use "{ 0 }" to initialize structures, use "{ }"

2011-08-03 06:25:42 Tree
[r4161] by proski

Don't use "{ 0 }" to initialize structures, use "{ }"

2011-08-03 05:43:55 Tree
[r4160] by proski

Fix dubious formatting after "if"

Found by coccinelle.

2011-08-03 01:30:00 Tree
[r4159] by proski

Remove useless cast of kmalloc() result

Found by coccinelle.

2011-08-03 01:22:41 Tree
[r4158] by proski

Fix dubious formatting after "if"

Found by coccinelle.

2011-08-03 01:20:36 Tree
Older >