Re: [ 00/20] 3.4.23-stable review
From: Shuah Khan <hidden>
Date: 2012-12-09 01:15:55
Also in:
lkml
On Sat, Dec 8, 2012 at 12:46 PM, Greg Kroah-Hartman [off-list ref] wrote:
On Fri, Dec 07, 2012 at 05:59:24PM -0700, Shuah Khan wrote:quoted
On Fri, Dec 7, 2012 at 5:52 PM, Shuah Khan [off-list ref] wrote:quoted
On Fri, Dec 7, 2012 at 5:49 PM, Shuah Khan [off-list ref] wrote:quoted
On Thu, Dec 6, 2012 at 5:54 PM, Greg Kroah-Hartman [off-list ref] wrote:quoted
This is the start of the stable review cycle for the 3.4.23 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Dec 9 00:50:03 UTC 2012. Anything received after that time might be too late. The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.4.23-rc1.gz and the diffstat can be found below. thanks, greg k-hPatche applied cleanly and compiled and booted on the following systems: HP EliteBook 6930p Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics Cross-compile tests alpha: defconfig passed arm: defconfig passed c6x: defconfig passed mips: defconfig passed mipsel: defconfig passed powerpc: wii_defconfig passed sh: defconfig passed sparc: defconfig passed tile: tilegx_defconfig passedCorrection. tile: tilegx_defconfig failed: tile tilegx_defconfig Just a snippet, I can send a full log. LD init/built-in.o HOSTCC usr/gen_init_cpio /home/shuah/lkml/linux_stable_testing_3.0.56/scripts/gen_initramfs_list.sh: Cannot open 'usr/contents.txt' make[1]: *** [usr/initramfs_data.cpio] Error 1 make: *** [usr] Error 2 Didn't get a chance to investigate.Sorry tile failure is for 3.0.56Is that caused by something new in 3.0.56, or has it always been that way?
Sorry forgot to mention that it is not a regression in 3.0.56. I compared the patch and this source file is not patched in 3.0.56-rc1. git log shows that this file was last touched back in Jan of 2011 and very likely this error was introduced in a commit from Sept 2010. You can choose to leave this in and I sent a patch which can go through its normal process and get pulled in when it gets approved by the powerpc maintainers. -- Shuah