From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-id: <52FBC226.8030607@samsung.com> Date: Wed, 12 Feb 2014 11:49:10 -0700 From: Shuah Khan Reply-to: shuah.kh@samsung.com MIME-version: 1.0 To: Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org, stable@vger.kernel.org, Shuah Khan , "shuahkhan@gmail.com" Subject: Re: [PATCH 3.13 000/120] 3.13.3-stable review References: <20140211184823.492407127@linuxfoundation.org> In-reply-to: <20140211184823.492407127@linuxfoundation.org> Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 02/11/2014 12:04 PM, Greg Kroah-Hartman wrote: > Some -stable releases spring out from my build system bright and shiny > and ready to go. Not so with these releases. Maybe it's the horrid > weather that was happening during the creation of these kernels, or > something else, but whatever it was, they came into this world > screaming, kicking, killing build servers left-and-right, and breaking > the build every other patch. Some developers decided to get into the > act, constantly pushing the boundaries of what is an acceptable -stable > patch, and trying to skirt the rules of upstream patches first numerous > times, making me even grumpier than normal, "forcing" me to relax and > take in an afternoon playing of the Lego movie... > > Test these out well, they have barely survived my systems, and I don't > trust them in the slightest to not eat your disks, reap your tasks, and > run away laughing as your CPU turns into a space heater. > > You have been warned. > > ----------------- > Worked fine on all my test systems. Compile tests and boot tests passed. No dmesg regressions: emerg, crit, alert, err are clean. No regressions in warn. -- Shuah -- Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) shuah.kh@samsung.com | (970) 672-0658