On Fri, Feb 08, 2013 at 09:36:05PM +0100, Johannes Berg wrote: > > There are still a couple bits of code present for older (<2.6.36 and <3.2) > > kernels, which I will strip out for inclusion in compat-drivers once > > this is mainlined. (Is there a better process I should follow here?) > > You should probably just submit it without those bits for the > wireless-next tree and then to the relevant compat-drivers patches as > needed. I'm now working on silencing checkpatch's complaints (about 3/4 done now); most of them revolve around the use of CamelCase variable names all over the place. In the process I'm doing other low-risk opportunistic cleanups. Once I'm done with that, I'll prepare another submission without the backwards compability bits, rebased against wireless-next. - Solomon -- Solomon Peachy pizza at shaftnet dot org Melbourne, FL ^^ (mail/jabber/gtalk) ^^ Quidquid latine dictum sit, altum viditur.
Attachment:
pgpSORQDRw55h.pgp
Description: PGP signature
