Bug 6143 - linux-yocto-3.10 needs SRCREV update in oecore/poky layer for mmc-sdhci-pci-fix
Summary: linux-yocto-3.10 needs SRCREV update in oecore/poky layer for mmc-sdhci-pci-fix
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: kernel (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.6.1
Assignee: Bruce Ashfield
QA Contact: Andra Necula
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-04-10 00:30 UTC by Drew Moseley
Modified: 2014-09-08 10:04 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Drew Moseley 2014-04-10 00:30:23 UTC
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.
Comment 1 Drew Moseley 2014-04-10 00:31:01 UTC
Sorry for the vagueness on this; I'm not terribly clear on the Yocto kernel mechanisms.
Comment 2 Darren Hart 2014-04-10 00:43:43 UTC
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.
Comment 3 Nitin Kamble 2014-04-10 00:48:31 UTC
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.
Comment 4 Nitin Kamble 2014-04-10 00:54:59 UTC
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
Comment 5 Bruce Ashfield 2014-04-10 02:56:16 UTC
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.
Comment 6 Drew Moseley 2014-04-10 12:09:12 UTC
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.
Comment 7 Bruce Ashfield 2014-04-10 12:32:32 UTC
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>
Comment 8 Bruce Ashfield 2014-04-10 12:33:09 UTC
The -stable updates may still make 1.6, I'm just waiting for the all clear from Richard before
sending more churn.
Comment 9 Darren Hart 2014-07-31 17:19:45 UTC
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
Comment 10 Andra Necula 2014-09-08 10:04:43 UTC
Verified, emenlow boots as we expected.