From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755304Ab3A0CPL (ORCPT ); Sat, 26 Jan 2013 21:15:11 -0500 Received: from mail-pa0-f54.google.com ([209.85.220.54]:63305 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755098Ab3A0CPJ (ORCPT ); Sat, 26 Jan 2013 21:15:09 -0500 Date: Sun, 27 Jan 2013 11:09:12 +0900 Message-ID: <87ham3fkc7.wl%satoru.takeuchi@gmail.com> From: Satoru Takeuchi To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk Subject: Re: [ 00/22] 3.4.28-stable review In-Reply-To: <20130124211504.701368763@linuxfoundation.org> References: <20130124211504.701368763@linuxfoundation.org> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/23.4 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 24 Jan 2013 13:15:21 -0800, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.4.28 release. > There are 22 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 Sat Jan 26 21:13:38 UTC 2013. > Anything received after that time might be too late. It' too late... anyway, this kernel can be built and boot without any problem. Building a kernel with this kernel also works fine. - 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 I reviewed the following patches and it looks good to me. > ------------- > Pseudo-Shortlog of commits: > > Greg Kroah-Hartman > Linux 3.4.28-rc1 ... > Konrad Rzeszutek Wilk > ACPI / cpuidle: Fix NULL pointer issues when cpuidle is disabled ... > Oleg Nesterov > wake_up_process() should be never used to wakeup a TASK_STOPPED/TRACED task ... > Steven Rostedt > ftrace: Be first to run code modification on modules Thanks, Satoru