Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1544317imu; Wed, 16 Jan 2019 22:28:48 -0800 (PST) X-Google-Smtp-Source: ALg8bN5FN3qCCI2gw6pFEnPYBFMunfxZf/UVyPEKRy7A6zuCk2/wcIHn3U4/srEaE7kiXZtgw0K0 X-Received: by 2002:a17:902:4222:: with SMTP id g31mr13668343pld.240.1547706528121; Wed, 16 Jan 2019 22:28:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547706528; cv=none; d=google.com; s=arc-20160816; b=M2i56zQ5oRzVZu13RjUzwV6/1D8/KMnwnBeFeQUu+XkuoffWyCMjlfdLHrduMrOth2 341bIiWnL5XzGfQcp0dB84V/PurvLeZ4RumdneaKgeSDV77zcwQMji1ElOIq/caqBprt AjHhRZduvO4TM/BVvU+HlwSQqDz/rdnN28VLxsh0kUwijDNOs5L4aUEln1y0S7Qr+rBO aNWerxB1Dw42DAGGWU5FK9NWZoyoGoT+sCHRJidXWIy+EAIxW+QTsa5QIToT+wO9WQgO rj7xsStZch6VrpGMG6WLGntzFYKDPDXTp+DMPxaz2CB1OFWuIXPFsUdUOa8Ty6ZJzc+f vFwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=1z5wGZKOyzTsup811Hp+wx00+YoU6L4EzroDpjtAYS0=; b=ZnMnR7mgGAkbh2T02ZY0hE6tmDfllRWP1HiJDg2hCNDR6Wlt4gOtvXRsj29r/9OvKo 3Ge/5rqYKqZkQeWuTpT2Se3+S0dJUppnRzQrjQ0+XRObWyE3246DyFsmaNn1OPK+gy9y nzU0bFP21C6ftQV0yvpv95QOV2KpAsolaRujtw8F+wfSZDH0bKML3IWGkZ0IZX6xjh/I kL38wD7H5Ry8/z5s9c/lPqEmnF/3233KIxuBkoyqxnQgaCCxLaeRszeIK81ZMj5lLUuP gM5r1/Be/7IwvRqoUN7EfK39JenJIvj6zFC0/eEK2R9WyEN3njQhuCTWj7TROytZ/BCT 83XQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QTtUbb8e; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g66si765661pgc.226.2019.01.16.22.28.32; Wed, 16 Jan 2019 22:28:48 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QTtUbb8e; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405848AbfAPRL6 (ORCPT + 99 others); Wed, 16 Jan 2019 12:11:58 -0500 Received: from mail.kernel.org ([198.145.29.99]:55294 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728496AbfAPRL6 (ORCPT ); Wed, 16 Jan 2019 12:11:58 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5FD8420651; Wed, 16 Jan 2019 17:11:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547658716; bh=Xv8tQ1PzEMDcd51TfoFUCHKVA/Gh9Mkxv0Bcdlx8Nag=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QTtUbb8eab0Hyx3NI85qhj3MQb1jviOzqT8T/mRCrbJJuS+A7sp5AmdfGMF4Y17Nt G1RbLuudw6O2op/OT8xf3huvs+JUUaK5ZGF1J1Wk4rvmGLdsjTqehsWvIl8MHRzMoa kThlJ+GaEm4SG9zJ5iPRuGeNL5XYO9Byr+hGBgEQ= Date: Wed, 16 Jan 2019 18:11:53 +0100 From: Greg Kroah-Hartman To: Jon Hunter Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org, stable@vger.kernel.org, linux-tegra Subject: Re: [PATCH 4.14 00/27] 4.14.94-stable review Message-ID: <20190116171153.GA10164@kroah.com> References: <20190115154901.189747728@linuxfoundation.org> <794339d5-a1f8-7ae1-8c8c-fbef141cc81d@nvidia.com> <20190116160252.GB4594@kroah.com> <26826b67-6a6b-dc79-84de-4ce48212203e@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26826b67-6a6b-dc79-84de-4ce48212203e@nvidia.com> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 16, 2019 at 04:56:08PM +0000, Jon Hunter wrote: > > On 16/01/2019 16:02, Greg Kroah-Hartman wrote: > > On Wed, Jan 16, 2019 at 09:25:12AM +0000, Jon Hunter wrote: > >> > >> On 15/01/2019 16:35, Greg Kroah-Hartman wrote: > >>> This is the start of the stable review cycle for the 4.14.94 release. > >>> There are 27 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 Thu Jan 17 15:48:28 UTC 2019. > >>> 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/v4.x/stable-review/patch-4.14.94-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-4.14.y > >>> and the diffstat can be found below. > >>> > >>> thanks, > >>> > >>> greg k-h > >> All tests are passing for Tegra ... > >> > >> Test results for stable-v4.14: > >> 8 builds: 8 pass, 0 fail > >> 16 boots: 16 pass, 0 fail > >> 14 tests: 14 pass, 0 fail > >> > >> Linux version: 4.14.94-rc1-gec31b1a > >> Boards tested: tegra124-jetson-tk1, tegra20-ventana, > >> tegra210-p2371-2180, tegra30-cardhu-a04 > > > > Thanks for testing two of these. > > > > How about 4.19 and 4.20? Does modern kernels work on this hardware as > > well? :) > > We are not that advanced yet ;-) So not everything for those platforms is upstream? :( > Only joking, absolutely and in fact we have more devices/boards > supported in newer kernels so it would make sense. We are also testing > mainline and -next. > > Unfortunately, it is a bit of a process to add new branches at the > moment simply because we are piggy backing on existing infrastructure > for testing that I personally do not own and so it needs to be approved. > However, nonetheless it is doable. > > We were talking about adding v4.19 and then v4.20 popped up. I am not > sure if you have any ideas yet about the EOL for v4.20? I was just > wondering if we should prioritise v4.20 now over v4.19? I was just curious, if everything was upstream (like the boards that linaro tests for), then running 4.19 should be just the same as 4.20. But if you have big out-of-tree patchsets, that's a totally different story. thanks, greg k-h