| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Jun 2009 21:16:05 -0400 From: Bob Copeland <bcopeland@...il.com> To: Jiri Slaby <jirislaby@...il.com> Cc: "John W. Linville" <linville@...driver.com>, linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org, ath5k-devel@...ema.h4ckr.net Subject: Re: [ath5k-devel] [PATCH 1/1] ath5k: fix beacon_int handling On Thu, Jun 18, 2009 at 9:14 PM, Bob Copeland<bcopeland@...il.com> wrote: >> 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? Err, nevermind, that's exactly what your patch does. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists