Re: [ 0/1] 3.4.33-stable review

From: Satoru Takeuchi <satoru.takeuchi@gmail.com>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [ 0/1] 3.4.33-stable review
Date: Wed, 20 Feb 2013 22:09:44 +0900	[thread overview]
Message-ID: <87hal7jfmv.wl%satoru.takeuchi@gmail.com> (raw)
In-Reply-To: <CAKocOOP4cBit5NOZzu3gyij7-xfODVP8wZ+qEAjA3gDNEObXHw@mail.gmail.com>

At Tue, 19 Feb 2013 20:31:02 -0700,
Shuah Khan wrote:
> 
> On Tue, Feb 19, 2013 at 7:51 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Feb 18, 2013 at 07:50:16PM -0700, Shuah Khan wrote:
> >> On Mon, Feb 18, 2013 at 11:24 AM, Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org> wrote:
> >> > This is the start of the stable review cycle for the 3.4.33 release.
> >> > There is 1 patch in this series, which will be posted as a response to
> >> > this one.  If anyone has any issues with it being applied, please let me
> >> > know.
> >> >
> >> > Responses should be made by Wed Feb 20 18:13:44 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.4.33-rc1.gz
> >> > and the diffstat can be found below.
> >> >
> >> > thanks,
> >> >
> >> > greg k-h
> >> >
> >> > -------------
> >>
> >> Patches applied cleanly to 3.0.65, and 3.4.32
> >> 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
> >>
> >> Reviewed patches
> >>
> >> Skipped Cross-compile tests
> >
> > Thanks for testing, your kernel log messages looked correct, right?
> >
> > greg k-h
> 
> Yes, should have mentioned that I checked dmesg and syslog both and
> compared dmesg
> with the old dmesg I saved from the previous rc-1 testing for each of
> these releases. Didn't
> see anything that jumped out at me. I usually save dmesg from rc
> cycles to look for regressions
> if any from one rc cycle to the next.

+1.

This kernel can be built and boot without any problem.
Building a kernel with this kernel also works fine.
* Its dmesg also looks correct. *

 - Build Machine: debian wheezy x86_64
   CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
   memory: 8GB

 - Test machine: debian wheezy x86_64(KVM guest on the Build Machine)
   vCPU: x2
   memory: 2GB

Thanks,
Satoru