On Mon, Jun 09, 2014 at 09:05:33AM -0700, Greg KH wrote: > On Mon, Jun 09, 2014 at 10:54:46AM -0500, Larry Finger wrote: > > On 06/09/2014 10:39 AM, Jes Sorensen wrote: > > >Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > > >>On Mon, Jun 09, 2014 at 03:15:52PM +0200, Jes.Sorensen@xxxxxxxxxx wrote: > > >>>From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> > > >>> > > >>>Greg, > > >>> > > >>>Thanks for pushing my other changes to Linus. This set goes on top of > > >>>the set I sent you on 2014/05/31 and the fix from 2014/06/03. If you > > >>>prefer I go back and submit it all as one large set, let me know. > > >>> > > >>>This set contains a number of fixes, including getting rid of some 'on > > >>>the wire' noise that isn't in the spec, plus removes a bunch of > > >>>functionality which is handled by the 802.11 stack, and shouldn't be > > >>>done within the driver. > > >>> > > >>>I hope there is still a change to get it all in through the 3.16 merge > > >>>window? > > >> > > >>76 patches is a lot for "bugfixes and reverts only" kernel releases. > > >> > > >>I know lots of these are cleanups, look at the first one listed: > > >> > > >>> staging: rtl8723au: rtw_get_wps_ie23a(): Remove unused dest pointer > > >>> wps_ie > > >> > > >>I don't feel comfortable justifying that to Linus or anyone about how > > >>important it is to get into 3.16-final, sorry. > > >> > > >>So, can you split this out into "bugfixes/regressions" and "cleanups, so > > >>I can apply them to the two different trees (for 3.16-final and for > > >>3.17-rc1.) > > > > > >OK, in that case, punt them for 3.17. The opening of 3.16 caught me a > > >bit by surprise to be honest, I thought I had another week or two. > > > > > >The previous set I sent you, I really would like in for 3.16 > > >though. That is a total of 13 commits. > > > > Jes and Greg, > > > > Linus wanted to issue 3.16-rc1 before he started his family vacation. The > > necessity of needing 3.15-rc8 interfered with that so he opened the merge in > > a temporary "next" branch of mainline, thus merging was already in progress > > when 3.15 was released. > > > > That said, patches 19 and 20 fix a firmware naming problem, and they should > > be included in 3.16, and backported to 3.15. > > Ok, I'll look into backporting those when I apply them, thanks. Any > others you feel should go into 3.16, please let me know. Those 2 applied cleanly, so I've added them to both of my branches now, thanks. greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
