From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:56227 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750822Ab2EBEGm (ORCPT ); Wed, 2 May 2012 00:06:42 -0400 Date: Wed, 02 May 2012 00:05:23 -0400 (EDT) Message-Id: <20120502.000523.307160882398092059.davem@davemloft.net> (sfid-20120502_060715_001220_768B91D1) To: linville@tuxdriver.com Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull request: wireless 2012-05-01 From: David Miller In-Reply-To: <20120501183157.GA2987@tuxdriver.com> References: <20120501183157.GA2987@tuxdriver.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: "John W. Linville" Date: Tue, 1 May 2012 14:31:58 -0400 > Part of these are Bluetooth -- Gustavo says: > > "A few more fixes to 3.4, there is three new device id supported, a missing > break and a fix to retain key during the connection." > > Along with those, we have some 802.11 fixes. Felix gives us a fix > for sending EAP frames for AP VLAN interfaces. Franky gives us > two brcmfmac fixes, one for missed event completions and another > for an improperly initialized function pointer. Grazvydas Ignotas > gives us a couple of wl1251 fixes for some improperly freed memory. > Jonathan Bither gives us an ath5k fix for an AHB resource leak. > Seth Forshee gives us a b43 fix to avoid a crash when b43 fails to > properly initialize. Finally, Wey-yi gives us a fixup for a previously > merged fix to use the correct firmware for certain iwlwifi devices. > > The brcmfmac fixes are bigger than I would like to see. But since > they are isolated to that driver and fix real problems, I felt they > were still acceptable. > > Please let me know if there are problems! Pulled, thanks John.