Re: [ 000/103] 3.10.3-stable review

[Shuah Khan]

> From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> Date: Tue, Jul 23, 2013 at 4:25 PM
> Subject: [ 000/103] 3.10.3-stable review
> To: linux-kernel@xxxxxxxxxxxxxxx
> Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>,
> torvalds@xxxxxxxxxxxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx,
> stable@xxxxxxxxxxxxxxx
>
>
> This is the start of the stable review cycle for the 3.10.3 release.
> There are 103 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 Thu Jul 25 22:01:33 UTC 2013.
> 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.10.3-rc1.gz
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
>
Patch applied cleanly to 3.10.2

Note: When I did a git reset --hard on 3.10.2-rc2 patch,
drivers/acpi/acpi_cmos_rtc.c was left as an untracked file.
I had to remove it before git pull succeeded for 3.10.2.

Compiled and booted on the following systems:

Samsung Series 9 900X4C Intel Corei5:
HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics:

dmesgs for all releases look good. No regressions compared to the 
previous dmesgs for each of these releases. dmesg emerg, crit, alert, 
err are clean. No regressions in warn.

Cross-compile testing:
HP Compaq dc7700 SFF desktop: x86-64 Intel Core-i2:

Cross-compile tests results:

alpha: defconfig passed
arm: defconfig passed
arm64: defconfig passed
c6x: defconfig passed
mips: defconfig passed
mipsel: defconfig passed
powerpc: wii_defconfig
sh: defconfig passed
sparc: defconfig passed
tile: tilegx_defconfig passed

-- Shuah

Shuah Khan, Linux Kernel Developer - Open Source Group Samsung Research 
America (Silicon Valley) shuah.kh@xxxxxxxxxxx | (970) 672-0658
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/