=== chris14_ is now known as chris14 [20:06] sarnold: you pointed me to the stable kernel patch docs, which is quite useful, but I'm looking to send a patch for the OEM kernel. [20:07] Do I just make a note that I want the patch I'm submitting to go to the OEM ekrnel in my email? [20:08] (the fix I want to integrate falls under "bug fixes" as mentioned in https://wiki.ubuntu.com/Kernel/OEMKernel it's not quite upstream-sanctioned yet, but it has been given a thumbs-up by me, my boss, and two upstream devs, so it looks like it's probably pretty likely to end up accepted into mainline.) [20:08] oh, wait, nevermind, I just answered my own question [21:18] arraybolt3: that's a level of detail I just don't know, but it's my understanding that the goal of the oem kernel is that things in ought to be sent upstream so the kernels can shrink, not that they should grow :) [21:18] I found the docs I needed. [21:19] Basically there's a fix still "going down the pipe" in mainline that my workplace needs *now*, and so having it in the OEM kernel will be a huge boon to us and the patch can go away not too long after. [21:19] (It's either that or build our own kernel from source for like a month, which is doable but highly undesirable.) [22:08] there isn't a whole lot of agility in our kernel process .. trying to move the patch through everything might take longer than getting it 'for free' if it hits the kernel stable tree [22:23] sarnold: it's already going to hit the kernel stable tree, if that ends up being faster then so be it. [22:24] Though then we get to build our own kernel for a month [22:24] :( [22:24] so I;m going to try to go through OEM first since this is its purpose. [22:26] arraybolt3: I mean, it might be worth following this path anyway, if it hasn't already been pulled into -stable, but .. I just didn't want you to wait a month and then find out that the stable release came too late and it'll be another month or something