From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f66.google.com ([209.85.214.66]:51180 "EHLO mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752012AbeDGVVr (ORCPT ); Sat, 7 Apr 2018 17:21:47 -0400 Received: by mail-it0-f66.google.com with SMTP id r19-v6so6351179itc.0 for ; Sat, 07 Apr 2018 14:21:47 -0700 (PDT) Date: Sat, 7 Apr 2018 16:21:44 -0500 From: Dan Rue To: Greg Kroah-Hartman Cc: Naresh Kamboju , open list , Linus Torvalds , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, linux- stable Subject: Re: [PATCH 4.16 00/31] 4.16.1-stable review Message-ID: <20180407212144.wyfgjesmildfvxqo@xps> References: <20180406084340.999820380@linuxfoundation.org> <20180407122815.GA2399@kroah.com> <20180407175427.GA23053@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180407175427.GA23053@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: On Sat, Apr 07, 2018 at 07:54:27PM +0200, Greg Kroah-Hartman wrote: > On Sat, Apr 07, 2018 at 10:37:33PM +0530, Naresh Kamboju wrote: > > >> Results from Linaro’s test farm. > > >> No regressions on arm64, arm and x86_64. > > >> > > >> Summary > > >> ------------------------------------------------------------------------ > > >> > > >> kernel: 4.16.1-rc1 > > >> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > >> git branch: linux-4.16.y > > >> git commit: 30380aa579224caf6a737160802151f466fe3953 > > >> git describe: v4.16-32-g30380aa57922 > > >> Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.16-oe/build/v4.16-32-g30380aa57922 > > >> > > >> No regressions (compared to build ) > > > > > > Compared to what build? :) > > > > There is no previous build to compare. > > stable-rc 4.16 is the new build in our system. > > This build results will act as base line for coming up 4.16 builds. > > Why were you all not testing 4.16-rc releases and the final 4.16.0 > release? For some reason I thought you all were doing that. Hi Greg - We track each branch separately and since linux-4.16.y is new, this was the first build. But, we tested 4.16 release on our mainline tracking branch (along with all the RCs and such before release). We have been testing all along, it just doesn't show up here because this is a new git branch and new qa-reports 'project'. In any case, we review all test failures to identify any issues, on all LTS branches, stable, mainline, and next. So, regardless of whether or not qa-reports identifies something as a 'regression', we'll notice it. Hope that helps, Dan