=== ivan\_ is now known as ivan\
=== smb` is now known as smb
=== rbasak_ is now known as rbasak
[14:33] <dannf> rtg: we have people wanting to play with xgene/utopic - mainly our linaro folks wanting to test out new arm64/kernel features - problem is they don't have luxuries like nic drivers, reboot support (still iterating in review upstream). question is, are you ok w/ carrying temporary versions of these drivers that we trade out w/ accepted versions later, or should i maintain a tree/ppa for them?
[14:34] <dannf> and is the answer different now vs. when we're nearing freeze?
[14:34] <rtg> dannf, you're talking about utopic ?
[14:34] <dannf> rtg: yes
[14:35] <rtg> dannf, you've got a few weeks yet that I can be flexible. As we get closer to freeze I'll clamp down on changes.
[14:36] <dannf> rtg: flexible meaning willing to take not-yet-upstream stuff, and clamp-down meaning no-more-swaps?
[14:36] <rtg> dannf, yup
[14:37] <dannf> rtg: ack
[14:37] <rtg> dannf, so, around Oct 1 I'll start to get more conservative. that said, the arm64 APM patches are quite testable.
[14:39] <dannf> rtg: do you know when you'll move to a 3.16-rc? after rc1?
[14:39] <rtg> dannf, it kindof depends on how stable it is. usually I'm not too comfortable inflicting a new kernel release on the real world until -rc2 or 3
[14:40] <rtg> -rc2 at the earliest for sure
[14:40] <dannf> ok. then we may ask for a few more cherry-picks for 3.15 in the meantime if that's ok. i'm also not sure what the best way to ask on-list for a cherry-pick is - if its a clean cherry-pick, do i need to attach patches, etc?
[14:41] <rtg> dannf, if they are clean then just the list of commits is fine. a pull request is best.
[14:42] <rtg> a pull request is _easiest_ for me to consume, regardless if they are clean cherry picks, etc.
[14:42] <dannf> rtg: ok
[14:42] <dannf> wfm
[17:02] <rtg> smb, could you check to see if Utopic still needs aabdb7729a2da806e60bf2d956f126e2cc3a0d85 (UBUNTU: SAUCE: kvm: Force preempt folding in kvm on i386) from Trusty ?
[17:04] <smb> rtg, I can. Gut feeling would be no, as there was a better but more invasive changeset mentioned, leading to the smal stable request
[17:04] <rtg> smb, cool, I'll ignore it for now
[17:05] <smb> Just have to figure out when those changes were in. ok, yeah
[17:08] <smb> rtg, ok, you can continue to ignore it for utopic as the four patches are in there. Only 3.13 and 3.14 were needing the other patch
[17:09] <rtg> smb, ack
[17:44] <rtg> dannf, does Utopic still need 'UBUNTU: [Config] CONFIG_TRANSPARENT_HUGEPAGE=n for arm64' ?
[17:55] <dannf> rtg: TBD. that's on my list to verify
[17:56] <dannf> the patches i was monitoring that were supposed to fix it never landed, but i saw another bug fix go in that might be the real problem
[17:56] <rtg> dannf, then I'll leave it out until further notice. just remember it if things get weird.
[17:56] <dannf> yep, will do. 
=== ming is now known as Guest58318
[21:07] <dmsmr_> I'm working on a kernel module and it triggers a BUG() as follows
[21:07] <dmsmr_> [ 1077.052029] kernel BUG at /build/buildd/linux-3.13.0/include/linux/scatterlist.h:65!
[21:07] <dmsmr_> How can I find out the code that triggers it?
[21:08] <dmsmr_> I've downloaded the kernel source but want to be sure about the line.
[21:09] <dmsmr_> Also, how can I find out my current kernel .config?
[21:10] <dmsmr_> Okay, config is under /boot
=== fmasi is now known as Guest75017