=== Ursinha-afk_ is now known as Ursinha | ||
=== Ursinha is now known as Guest82331 | ||
=== inaddy is now known as tinoco | ||
=== rsalveti_ is now known as rsalveti | ||
=== psivaa_ is now known as psivaa | ||
=== cnd_ is now known as cnd | ||
=== broder_ is now known as broder | ||
=== Guest82331 is now known as Ursinha | ||
=== Ursinha is now known as ursula1234 | ||
=== ursula1234 is now known as Ursinha | ||
=== niedbalski_ is now known as niedbalski | ||
catbus1 | Dear Ubuntu kernel team, I am working with the Cisco SNIC (SCSI NIC) team. SNIC is a new driver accepted in upstream 4.2.4. I see our latest Wily kernel is based on upstream 4.2.3. Can someone please tell me about when we will be based on 4.2.4? Or should I work with them to submit a patch to Ubuntu kernel? | 17:25 |
---|---|---|
henrix | catbus1: 4.2.4 (and 4.2.5) patches should be applied to the wily kernel soon(ish). next week we start a new 3-week SRU cycle, and usually apply stable patches to our kernels during the 1st week | 17:37 |
catbus1 | henrix: Thank you. One more question, is a new driver consider a stable patch? It's accepted in 4.2.4: http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=24136f 2c0b3bd55d98bdfe097331a4ab7eb1869b | 17:39 |
catbus1 | probably this is a better link: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/scsi/snic?id=refs/tags/v4.2.4 | 17:41 |
henrix | catbus1: new drivers/features are not acceptable for stable kernels. but the wily kernel is *not* a stable kernel -- we simply apply upstream 4.2 stable kernel patches, but it has lots of other ubuntu-specific patches | 17:44 |
catbus1 | henrix: Just want to make sure I fully understand this. So snic will be in wily kernel after the next SRU cycle. The wily kernel will become HWE kernel for 14.04 in Jan/Feb. The snic driver will be in-box in 14.04.4, right? | 17:57 |
henrix | catbus1: correct. and although i'm just not sure about the next 14.04 point-release dates, it's likely that the linux-lts-wily kernel will be available before that ;) | 18:01 |
catbus1 | henrix: Great, thank you very much. | 18:02 |
rtg | kamal, http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=2459ee8651dc5ab72790c2ffa99af288c7641b64 should go to 4.2 stable | 18:03 |
kamal | rtg, 4.2-stable is still gregkh's responsibility. That commit bears a Fixes: line, but the commit it says it fixes didn't land until 4.3-rc1 ... | 18:17 |
kamal | rtg, so how sure are you that its actually relevant for 4.2? I expect that gregkh will _not_ apply that one to 4.2 automatically. | 18:18 |
rtg | kamal, I've already submitted the patch on the k-team list. It appears to fix an issue related to bug #1499089 | 18:20 |
ubot5 | bug 1499089 in linux (Ubuntu Wily) "Please enable kconfig X86_LEGACY_VM86 for i386" [Wishlist,Fix released] https://launchpad.net/bugs/1499089 | 18:20 |
kamal | rtg, ok relevant for wily, but not for 4.2 mainline -- got it. ok, issue resolved :-) | 18:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!