Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1224277imu; Wed, 16 Jan 2019 15:09:13 -0800 (PST) X-Google-Smtp-Source: ALg8bN796hVLNcc7+fYdPDNKdz+PIyBLBmD6YEWQ83WzXQGs9WgrbRebUc5ik3paskFUtNTfeJXv X-Received: by 2002:a17:902:e012:: with SMTP id ca18mr12365237plb.218.1547680153074; Wed, 16 Jan 2019 15:09:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547680153; cv=none; d=google.com; s=arc-20160816; b=rtrRX0SU5SG4y5WkyefiYM7Ga6KAgKiSHxnWSyWZD01BQtuSeLn41ScY8/P6RLnH8s 9SJUdaNHrqILmmhA4cnCFmarWj01TcYtPwPUzr2YUGSuAaBWUspj0DV38ILMU632TAGI /4qaFhVKxl/8+q/gWTVPkHNSPUl/bw5NRbthHOJJOg09r/u7kRlynXhUJg4ASXHLp6ot EYPvaF0L7e174K4MWE9cIMM5nJd4wkDHiLXLZuPpgY8bE+sUe2s0AzL103TlTay0ckge 7m+ms+rGMjYlm8z/kZmKg8BXUket2BajI7waDQJX/DF255xMSH8x9K5Xu7MEMaJwPW6V dGTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=S3riZj14QbvPRGQOjxNw0RcHdULFJZnkGxh9helIbI8=; b=lT2iRvPXoUx+bx4WNQjkSb/FlxNoE7t3fn3KG+W3Tv6SxYqO29ZAeWofwuDPsHLhKX wBEwRSGFyXJuBdaNaFxFSzhlsAvtyIH9Pyipqi8UINTXggogmalCrGCwY6jdpmUwmIAq HuHZA0XKyEEF/PaedrFWP59InjcOs3gJ3D5FItQ96lG408cvM8r87UcCuiR/1Bg0fz0u nwlUh3h8u35QDKKXx3ZGckH05p259GUfV88BRC2tqHkd8pxFKIVFKyhKpGG7bmLPnP4a jLe4yjvE/TcgkxKnWPe6t15yuq88+vHvwhCLz/h3OrKdKc7k3NQe7ZHAP1fuUkuGM+G7 zvYA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b="dffO/BNu"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q140si9245433pfc.20.2019.01.16.15.08.57; Wed, 16 Jan 2019 15:09:13 -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=@nvidia.com header.s=n1 header.b="dffO/BNu"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2394387AbfAPQ4O (ORCPT + 99 others); Wed, 16 Jan 2019 11:56:14 -0500 Received: from hqemgate14.nvidia.com ([216.228.121.143]:6531 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388464AbfAPQ4N (ORCPT ); Wed, 16 Jan 2019 11:56:13 -0500 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Wed, 16 Jan 2019 08:55:58 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Wed, 16 Jan 2019 08:56:13 -0800 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Wed, 16 Jan 2019 08:56:13 -0800 Received: from [10.21.132.148] (172.20.13.39) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 16 Jan 2019 16:56:10 +0000 Subject: Re: [PATCH 4.14 00/27] 4.14.94-stable review To: Greg Kroah-Hartman CC: , , , , , , , , , linux-tegra References: <20190115154901.189747728@linuxfoundation.org> <794339d5-a1f8-7ae1-8c8c-fbef141cc81d@nvidia.com> <20190116160252.GB4594@kroah.com> From: Jon Hunter Message-ID: <26826b67-6a6b-dc79-84de-4ce48212203e@nvidia.com> Date: Wed, 16 Jan 2019 16:56:08 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20190116160252.GB4594@kroah.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL103.nvidia.com (172.20.187.11) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1547657758; bh=S3riZj14QbvPRGQOjxNw0RcHdULFJZnkGxh9helIbI8=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=dffO/BNugwLR5gduEkHH0mhpzXiEl4TN1KO2ulyHo94VfFnnfj62FFp+6FT7E3i8A Nt7htHKjCK0XlkCWOnDq/ufxLvvIgs1jcOd5Hj8YHm35uh9D6/SYcDwMbnYjMHiADq BSSmoypaW/0KcgoWMMs5E9fbxJCRhRWhJAiEv1VmOnrsfxJeLHv2V9SUb36UIIJikl UTJXFuPTbWDuVavnG/qmSj4uRcAMYhIK0Tp6nPGxZBIdPbeNcSoxhKjj2N51M+aTNa kpooSlBTC720eHkhMEvYKdo+P9qW7VMl3vaIYB2BHBPDz7zfHtIYDWW9SQpjJth8Nm d4Aw7dPGBd7vg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 ;-) 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? Cheers Jon -- nvpublic