On Sat, Jun 21, 2014 at 10:20:12PM +0200, Jes Sorensen wrote: > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > > On Sat, Jun 21, 2014 at 04:50:08PM +0200, Jes.Sorensen@xxxxxxxxxx wrote: > >> From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> > >> > >> Greg, > >> > >> Thanks for merging the last set. I starting going through the code > >> again, and removed a pile of dead code (patches 1-7). > >> > >> However in the process I noticed a couple of cases where raw beacon > >> frame information was copied to a new wlan network struct, but the > >> retrieved information wasn't, which can leave to trying to access the > >> network with parameters that do not match that of the access point > >> (patches 8-9). > >> > >> There is also a fix for a case where we in AP mode would send out a > >> corrupted frame on the wire (patch 10). > >> > >> Patch 11 is a simple cleanup. > >> > >> It would be nice if it can all make it into staging-next, but if not, > >> 8, 9, and 10 are rather serious and really need to go in. > > > > There's no problem getting anything into staging-next for a next few > > weeks until 3.16-rc7 or so. > > Great, thanks! I got a little confused since I saw two branches showing > up again when I pulled the latest staging tree :) The staging-next branch is for the "next" kernel release, 3.17-rc1. staging-linus is for this release, 3.16-final. If you have fixes you want in 3.16, please make them against that branch and let me know when you send them to me which to apply them to. Hope this helps, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
