From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:44356 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949AbeDGGKI (ORCPT ); Sat, 7 Apr 2018 02:10:08 -0400 Date: Sat, 7 Apr 2018 08:10:06 +0200 From: Greg Kroah-Hartman To: Harsh Shandilya Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org, stable@vger.kernel.org Subject: Re: [PATCH 3.18 00/93] 3.18.103-stable review Message-ID: <20180407061006.GC18744@kroah.com> References: <20180406084224.918716300@linuxfoundation.org> <44CEAA8A-8B4C-47D0-A5A6-F8144EADE310@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44CEAA8A-8B4C-47D0-A5A6-F8144EADE310@gmail.com> Sender: stable-owner@vger.kernel.org List-ID: On Sat, Apr 07, 2018 at 12:41:38AM +0530, Harsh Shandilya wrote: > > > On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman wrote: > >This is the start of the stable review cycle for the 3.18.103 release. > >There are 93 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 Sun Apr 8 08:42:04 UTC 2018. > >Anything received after that time might be too late. > > > >The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.103-rc1.gz > >or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >linux-3.18.y > >and the diffstat can be found below. > > > >thanks, > > > >greg k-h > > Builds and boots on the OnePlus3T, no visible regressions. The merge was slightly gnarly with "proc: revert /proc//maps [stack:TID] annotation" conflicting due to kernel-common changes and the v4l2 series conflicting with CAF changes in the msm-3.18 tree. Yeah, the merge is going to be a bit messy, not as messy as 4.9.y is going to be :) Thanks for testing and letting me know. greg k-h