[10:24] <tseliot> apw: hi. Shall I fix the binary blobs for Linux 4.2 in the PPA? Also, does that include rtg's commit for the workqueue?
[10:25] <apw> tseliot, i believe his change is applied, checking
[10:25] <apw> tseliot, yes -3.3 has it
[10:25] <tseliot> apw: excellent
[10:26] <apw> tseliot, and yes shove those in the PPA to get that
[10:26] <apw> or indeed feel free to copy them out with binaries into your own PPA
[10:26] <apw> that also works
[10:26] <tseliot> yes, I only need to grab the packages for my chroot to see what broke
[10:29] <apw> as i assume they can go into -proposed first
[10:29] <apw> and indeed should if possible
[10:30] <tseliot> right
[10:44] <tseliot> apw: fglrx doesn't seem to fail here with 4.2
[10:44] <apw> tseliot, great
[10:44] <tseliot> I'll try the nvidia drivers
[10:44] <apw> tseliot, the nvidia ones claim to work on the matrix
[10:44] <tseliot> err... my nvidia 352 is still stuck in NEW
[10:44] <apw> but not fgrlx
[10:45] <apw> http://people.canonical.com/~kernel/info/dkms/int-matrix.html
[10:45] <apw> so that is rather odd
[10:47] <tseliot> apw: it only seems to fail on i386
[10:47] <apw> tseliot, oh, odder
[10:48] <apw> tseliot, and indeed that is what the matrix says too
[10:48] <tseliot> error: implicit declaration of function â€˜__xgâ€™
[10:48] <tseliot> which, garbage aside, is  : "q"(new), "m"(*__xg(ptr)), "0"(old)
[10:52]  * tseliot needs to create an i386 wily chroot...
[10:54] <apw> tseliot, new compiler perhaps
[10:55] <apw> oh .. an actual removed __foo thing
[10:55]  * tseliot nods
[10:59] <om26er> on wily bcmwl fails to build if I install linux 4.2 rc6: here are the logs http://paste.ubuntu.com/12054833/
[10:59] <om26er> anyway to workaround/fix that ?
[11:00] <apw> om26er, there is an upstream fix coming for that which is appplied to our 4.2 kernel in the ckt PPA
[11:00] <apw> tseliot, i didn't realise the fix for nvidia also fixed brcm
[11:01] <tseliot> apw: IIRC rtg said he fixed bcmwl (?)
[11:02] <om26er> apw, great, I'll install from there.
[11:02] <apw> tseliot, he may have fixed it by fixing the kernel, or it had two issues and the second was already fixed by nvidia
[11:03] <tseliot> right
[11:03] <tseliot> well, it's always a win when I don't have to fix things myself ;)
[11:09] <TJ-> Oh, you're on about the flush_workqueue() licence change? I reported it originally back in June but haven't kept track - has 4.2 mainline fixed it?
[11:13] <apw> TJ-, it wasn't technically a flush_workqeue licence change, it was a caller becoming inline
[11:13] <apw> but yes that is the one we are talking about
[11:14] <apw> a fix for it seems to have been taken by the sub-system maintainer, but clearly is not in -rc6
[11:14] <TJ-> apw: yeah I know, but that was the effect
[11:15] <TJ-> OK ... thanks... I only found it because I was building 4.2 with some major PCI subsystem fixes for testing and the nvidia driver failed to build
[12:33] <apw> yeah that'd do it indeed
[14:37] <unixabg> apw: Greetings just checking in on the overlayfs and casper (or so I think but I could be wrong) status.
[16:07] <jsalisbury> ##
[16:07] <jsalisbury> ## Kernel team meeting today @ 17:00 UTC
[16:07] <jsalisbury> ##
[16:54] <jsalisbury> ##
[16:54] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:54] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
[17:12] <cristian_c> jsalisbury: hello
[17:15] <cristian_c> jsalisbury: I'd like to know if you have contacted the author of commit
[20:16] <gQuigs> there's no ubuntu/ubuntu-wily.git?  where could I get the ubuntu kernel config for wily? - http://kernel.ubuntu.com/git  (Ideally I'd just want to know the difference between it and 14.10) 
[20:30] <apw> gQuigs, there is a git repo for it, its in launchpad, we are starting to migrate, very very slowly
[20:30] <apw> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily  iirc
[20:31] <gQuigs> apw: oh.. awesome; thanks!