6143 2014-04-10 00:30:23 +0000 linux-yocto-3.10 needs SRCREV update in oecore/poky layer for mmc-sdhci-pci-fix 2014-09-08 10:04:43 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel unspecified x86 Multiple VERIFIED FIXED Medium+ normal 1.6.1 1 drew bruce.ashfield andrax.g.necula bruce.ashfield dvhart nitin.a.kamble sjolley.yp.pm tom.zanussi andrax.g.necula --- --- No (bug/feature does not impact docs) oldest_to_newest 42485 0 drew 2014-04-10 00:30:23 +0000 The bug being discussed here: https://patchwork.kernel.org/patch/3926081/ is present in the current poky linux-yocto_3.10 recipe. In speaking with Nitin K on irc, he indicated that the v3.10 kernel recipes in poky need srcrev updates to get this fix from v3.10.35 LTSI. 42486 1 drew 2014-04-10 00:31:01 +0000 Sorry for the vagueness on this; I'm not terribly clear on the Yocto kernel mechanisms. 42487 2 dvhart 2014-04-10 00:43:43 +0000 Thanks Drew. I've updated the subject and assigned back to Nitin. We don't typically track these via BZ as it's easy enough just to send a two line patch usually - but if it's been lagging (as people are swamped currently) this is a reasonable way to track it. 42488 3 nitin.a.kamble 2014-04-10 00:48:31 +0000 I would like to clarify this issue is for not meta-intel, It is for the SRCREVS in the poky. To be specific in these files: meta/recipes-kernel/linux/linux-yocto_3.10.bb meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.10.bbappend Bruce does validation with different platforms for such changes. so I will pass the bug to Bruce. 42489 4 nitin.a.kamble 2014-04-10 00:54:59 +0000 Drew, BTW, you can use the new intel-core2-32 or intel-corei7-64 BSP from meta-intel layer, which already has the fix you need. Nitin 42494 5 bruce.ashfield 2014-04-10 02:56:16 +0000 Yes. Please no bugs for -stable updates. They are a matter of procedure and are always a task that gets done at the appropriate time. As for right now, I already have all the -stable updates staged, but I'm not pushing anything to Richard since we can't take *any* unexpected breakage since we are close to the release. I'll have a full slate of -stable updates once 1.6 releases. 42514 6 drew 2014-04-10 12:09:12 +0000 Let me back up a bit. My original question was to determine if there was any chance this bug fix would make it in time for 1.6. Sounds like that's not going to happen correct? If so I'll put it in my local layer. 42518 7 bruce.ashfield 2014-04-10 12:32:32 +0000 If you are only interested in the one change as a priority, I've had it in the linux-yocto-3.10 tree for quite some time. commit 8d4d5975e5921a2f405f53211d1a27acab9bba56 Author: Adrian Hunter <adrian.hunter@intel.com> Date: Tue Jan 21 09:52:39 2014 +0200 mmc: sdhci-pci: Fix possibility of chip->fixes being null It is possible for chip->fixes to be null. Check before dereferencing it. Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> Cc: stable <stable@vger.kernel.org> # 3.11+ Signed-off-by: Chris Ball <chris@printf.net> 42519 8 bruce.ashfield 2014-04-10 12:33:09 +0000 The -stable updates may still make 1.6, I'm just waiting for the all clear from Richard before sending more churn. 44899 9 dvhart 2014-07-31 17:19:45 +0000 Resolved in: commit 4f6259987f2c2bf4b81b6dfe712ae2fb8f18fc53 Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: 2014-04-02 linux-yocto/3.10: v3.10.35 and emenlow boot fixes 45436 10 andrax.g.necula 2014-09-08 10:04:43 +0000 Verified, emenlow boots as we expected.