From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933300AbdKPECP (ORCPT ); Wed, 15 Nov 2017 23:02:15 -0500 Received: from mail-lf0-f48.google.com ([209.85.215.48]:50092 "EHLO mail-lf0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932401AbdKPECH (ORCPT ); Wed, 15 Nov 2017 23:02:07 -0500 X-Google-Smtp-Source: AGs4zMb5St4riEzcbny/3vZ1Z/aZBJ7o1zshk7zb7V+8YZO4q/CccI/XQAjpA5YFXU08bAsF23pMCP+KJOan3CQMVSI= MIME-Version: 1.0 In-Reply-To: References: <20171109120842.GA27875@kroah.com> <1510231236.2748.163.camel@decadent.org.uk> <20171109124814.GA25832@kroah.com> From: Kevin Hilman Date: Wed, 15 Nov 2017 20:02:04 -0800 Message-ID: Subject: Re: [PATCH 3.16 000/294] 3.16.50-rc1 review To: Arnd Bergmann , Greg KH Cc: Ben Hutchings , Linux Kernel Mailing List , "# 3.4.x" , Linus Torvalds , Guenter Roeck , Andrew Morton , "kernelci.org bot" , Matt Hart Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 14, 2017 at 12:55 PM, Arnd Bergmann wrote: > On Tue, Nov 14, 2017 at 9:35 PM, Kevin Hilman wrote: >> On Thu, Nov 9, 2017 at 5:35 AM, Arnd Bergmann wrote: >>> On Thu, Nov 9, 2017 at 1:48 PM, Greg KH wrote: >>>> On Thu, Nov 09, 2017 at 12:40:36PM +0000, Ben Hutchings wrote: >>>>> On Thu, 2017-11-09 at 13:21 +0100, Arnd Bergmann wrote: >>>>> > On Thu, Nov 9, 2017 at 1:08 PM, Greg KH wrote: >>>>> > > On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote: >>>>> [...] >>>>> > > > I think if you upload the branch to the stable-rc git, that should produce >>>>> > > > the automated build and boot results via email or via the >>>>> > > > https://kernelci.org/job/ interface. Once there are some results >>>>> > > > there, I'll go through the list once more to see what warnings >>>>> > > > and failures remain. >>>>> > > >>>>> > > I don't know of a way to have others push to that tree/branch at the >>>>> > > moment :( >>>>> > > >>>>> > > I'll go update that branch now... >>>>> > >>>>> > Thanks! >>>>> > >>>>> > With the arm-soc tree, we simply have a shared group-id on >>>>> > gitolite.kernel.org and everyone in that group can push to it. >>>>> > >>>>> > If that is the only thing you need, it should be trivial to let Ben >>>>> > and Sasha push to /pub/scm/linux/kernel/git/stable/*.git as well, >>>>> > I'm sure helpdesk@kernel.org can arrange that. Of course if you are >>>>> > worried about having multiple accounts with write access to all the >>>>> > branches, then that wouldn't be enough. >>>>> >>>>> I think I'd rather send a pull request to Greg at the start of the >>>>> review period. >>>> >>>> That works for me! >>> >>> We just discussed this on the #kernelci IRC channel. Since kernelci >>> has a whitelist of branches and 3.16 isn't currently on it, how about >>> just adding a different git tree for Ben's 3.2-rc and 3.16-rc releases? >> >> We are currently reaching the limits of our current build capacity, so >> want to understand the users before adding more trees. >> >> That being said, it seems Ben is now pushing to Greg's stable-rc, so >> we can pretty easily add linux-3.16.y to our list of stable-rc >> branches if there is enough interest. Also, we would much prefer >> monitoring a git branch, since kernelci does not currently deal with >> git + quilt (and we have no time, and less motivation to add it) :) > > Ben does not push to Greg's stable-rc, that was a mistake on my > side, Any reason not to push to Greg's stable-rc (or have Greg pull)? It would be a lot simpler from our side if we didn't have to track the various stable tree maintainers. Kevin