Re: [ath5k-devel] [PATCH 1/1] ath5k: fix beacon_int handling

From: Bob Copeland
Date: Thu Jun 18 2009 - 21:15:07 EST


On Thu, Jun 18, 2009 at 7:06 PM, Jiri Slaby<jirislaby@xxxxxxxxx> wrote:
> 73ca5203366235f8a43e490767284ba8cfd8c479
> (ath5k: remove conf->beacon_int usage)
> removed bintval setting from ath5k_config. We need to init the
> interval earlier and don't touch it in add_interface anymore.
>
> Otherwise it will be set only once by upper layer through
> bss_info_changed but not on second and further hostap executions.

Shouldn't we just not destroy the value in add_interface?

I thought conf->beacon_int was deprecated.

--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/