Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933003AbdDQI0y (ORCPT ); Mon, 17 Apr 2017 04:26:54 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:51684 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932355AbdDQI0v (ORCPT ); Mon, 17 Apr 2017 04:26:51 -0400 Date: Mon, 17 Apr 2017 10:26:35 +0200 From: Greg Kroah-Hartman To: Amit Pundir Cc: Guenter Roeck , lkml , torvalds@linux-foundation.org, Andrew Morton , shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, stable@vger.kernel.org Subject: Re: [PATCH 3.18 000/145] 3.18.49-stable review Message-ID: <20170417082635.GA3931@kroah.com> References: <20170416080200.205458595@linuxfoundation.org> <20170417065653.GD21022@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.1 (2017-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3250 Lines: 69 On Mon, Apr 17, 2017 at 01:37:00PM +0530, Amit Pundir wrote: > On 17 April 2017 at 12:26, Greg Kroah-Hartman > wrote: > > On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote: > >> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote: > >> > This is the start of the stable review cycle for the 3.18.49 release. > >> > There are 145 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. > >> > > >> > --------- > >> > Wait, what? 3.18? Wasn't that kernel dead and forgotten and left to > >> > rot on the side of the road? Yes, it was, but unfortunately, there's a > >> > few million or so devices out there in the wild that still rely on this > >> > kernel. Now, some of their manufacturers and SoC vendors might not be > >> > keeping their kernels up to date very well, but some do actually care > >> > about security and their users, so this release is for them. If you > >> > happen to have a vendor that does not care about their users, go > >> > complain, as odds are, your device is very insecure right now... > >> > > >> > Because of this strange situation, and thanks to some vendors backing > >> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing > >> > releases every once in a while to keep it up to date and working well > >> > based on what is happening in other more well-maintained stable kernels > >> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so, > >> > switch vendors, it's the only way they will learn...) I don't know how > >> > long I'll keep doing this, so if you care about 3.18, please contact me > >> > to let me know the expected lifespan of your device. > >> > > >> > And finally, due to the delay from the last 3.18-stable kernel release, > >> > there is a large backlog of patches, this is about 1/2 of the pending > >> > ones so far. I'll be working on catching up to the rest of them over > >> > the next few weeks, and then the updates should be smaller than this > >> > one. > >> > > >> > ok, back to your normal form-letter stable -rc release notice: > >> > --------- > >> > > >> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017. > >> > Anything received after that time might be too late. > >> > > >> > >> Build results: > >> total: 140 pass: 139 fail: 1 > >> Failed builds: > >> parisc:allmodconfig > >> > >> Qemu test results: > >> total: 111 pass: 111 fail: 0 > >> > >> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix > >> MODULE_DEVICE_TABLE invocation"). > > > > Ah, nice! I'm pretty amazed that there was only one failure, thanks for > > testing all of these and letting me know. I've also queued up this last > > patch for 3.18. > > Can you please pick this one > https://www.spinics.net/lists/stable/msg166162.html as well. It fixes > ARCH=arm + CONFIG_SMP=n + CONFIG_ARM_PSCI=y builds. It's in my long-pending queue for 3.18 patches, I'll catch it the next release. Give me a chance to catch up with everything (again, I have well over 200+ patches left to dig through), before you start sending me new 3.18-stable patches please :) thanks, greg k-h