[linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Thanks, Nitin The following changes since commit c7739be126930006e3bfbdb2fb070a967abc5e09: drm/mm: include required headers in drm_mm.h (2014-03-27 13:06:47 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib nitin/ltsi http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/ltsi Nitin A Kamble (1): sdhci-pci.c: a fix for invalid memory access drivers/mmc/host/sdhci-pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
-Original Message- From: Hart, Darren Sent: Monday, March 31, 2014 1:34 PM To: Kamble, Nitin A; Ashfield, Bruce (Wind River); linux- yo...@yoctoproject.org Subject: Re: [PATCH 0/1] a fix for v3.10 LTSI branch On 3/31/14, 13:24, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Is this a backport from mainline? If so, it needs the cherry-pick ID. If not, this needs to go upstream first and then back to 3.10 stable (which LTSI will pick up). If neither of these seems like the right approach to you - what did you have in mind and why? This is not a backport. But I am planning to send it to LTSI upstream. As you say this will be back ported, once it goes upstream in the LTSI repo. Nitin Thanks, -- Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
On 3/31/14, 13:56, Kamble, Nitin A nitin.a.kam...@intel.com wrote: -Original Message- From: Hart, Darren Sent: Monday, March 31, 2014 1:34 PM To: Kamble, Nitin A; Ashfield, Bruce (Wind River); linux- yo...@yoctoproject.org Subject: Re: [PATCH 0/1] a fix for v3.10 LTSI branch On 3/31/14, 13:24, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Is this a backport from mainline? If so, it needs the cherry-pick ID. If not, this needs to go upstream first and then back to 3.10 stable (which LTSI will pick up). If neither of these seems like the right approach to you - what did you have in mind and why? This is not a backport. But I am planning to send it to LTSI upstream. As you say this will be back ported, once it goes upstream in the LTSI repo. Please do not send it to LTSI. LTSI is not a development target. LTSI tracks stable and gets new features *from mainline* that stable cannot. Please send this to lkml with the stable line included (see the stable-kernel-rules.txt). This should get picked up into the LTSI release as a matter of course after it lands in 3.10 stable. -- Darren Hart Yocto Project - Linux Kernel Intel Open Source Technology Center -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/1] a fix for v3.10 LTSI branch
On 3/31/2014 2:01 PM, Hart, Darren wrote: On 3/31/14, 13:56, Kamble, Nitin A nitin.a.kam...@intel.com wrote: -Original Message- From: Hart, Darren Sent: Monday, March 31, 2014 1:34 PM To: Kamble, Nitin A; Ashfield, Bruce (Wind River); linux- yo...@yoctoproject.org Subject: Re: [PATCH 0/1] a fix for v3.10 LTSI branch On 3/31/14, 13:24, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com I was noticing emenlow BSP failing to boot since LTSI was integrated in the v3.10 kernel. After debugging I found out that kernel code was doing an invalid memory access, causing kernel panic. Here is the fix for the issue, which I am also pushing to the upstream v3.10 LTSI kernel repository. Is this a backport from mainline? If so, it needs the cherry-pick ID. If not, this needs to go upstream first and then back to 3.10 stable (which LTSI will pick up). If neither of these seems like the right approach to you - what did you have in mind and why? This is not a backport. But I am planning to send it to LTSI upstream. As you say this will be back ported, once it goes upstream in the LTSI repo. Please do not send it to LTSI. LTSI is not a development target. LTSI tracks stable and gets new features *from mainline* that stable cannot. Please send this to lkml with the stable line included (see the stable-kernel-rules.txt). This should get picked up into the LTSI release as a matter of course after it lands in 3.10 stable. Got it. I pulled the trigger for LTSI ML too fast then. I will post it on LKML for 3.10 stable now. Thanks for the clarification. Nitin -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
