From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 086048B1 for ; Sun, 9 Sep 2018 04:36:17 +0000 (UTC) Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-eopbgr710113.outbound.protection.outlook.com [40.107.71.113]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 57D4B8D for ; Sun, 9 Sep 2018 04:36:16 +0000 (UTC) From: Sasha Levin To: Greg Kroah-Hartman Date: Sun, 9 Sep 2018 04:36:14 +0000 Message-ID: <20180909043612.GM16300@sasha-vm> References: <20180907150623.GH16300@sasha-vm> <9fb15d7c-c59f-ee21-9c30-6d81d53a1456@redhat.com> <20180907160945.GI16300@sasha-vm> <20180907202328.GE25756@kroah.com> <20180907211341.GJ16300@sasha-vm> <20180907224346.GA21546@roeck-us.net> <20180907225744.GL16300@sasha-vm> <20180908163351.GD11120@kroah.com> In-Reply-To: <20180908163351.GD11120@kroah.com> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, Sep 08, 2018 at 06:33:51PM +0200, Greg Kroah-Hartman wrote: >On Fri, Sep 07, 2018 at 10:57:45PM +0000, Sasha Levin via Ksummit-discuss = wrote: >> On Fri, Sep 07, 2018 at 03:53:08PM -0700, Linus Torvalds wrote: >> >On Fri, Sep 7, 2018 at 3:43 PM Guenter Roeck wrote= : >> >> >> >> On Fri, Sep 07, 2018 at 03:27:01PM -0700, Linus Torvalds wrote: >> >> > >> >> > So maybe an automated "linux-next" that starts happening *before* t= he >> >> > rc stage would catch some things? >> >> >> >> And it does, as soon as Greg publishes a set of patches. >> > >> >Yes, yes, I was clearly not explaining myself well. >> > >> >I see all the reports that you (and Nathan, and Shuah, and others) do >> >for stable rc's. So I very much know that happens. >> > >> >But I was literally thinking of that week or two *before* Greg >> >actually picks up the stable patches because he wants to have them get >> >some testing in mainline first. >> > >> >*If* the same kinds of scripts that Greg and Sasha already use to pick >> >up their stable patches could be automated early, maybe the patches >> >would also get a bit of special testing in the *context* of the stable >> >tree? A special automated "these are marked for stable, but haven't >> >been picked up yet" stable-next testing thing? >> >> I agree. This is what I was suggesting with stable-next branches. > >Ok, this sounds semi-reasonable. I'll knock something up this week to >see if it's viable to do automated and then have it get sent to 0-day to >do a basic "smoke test". > >let's see how that works... I've pushed an autogenerated branch for 4.14 here: https://git.kernel.org/p= ub/scm/linux/kernel/git/sashal/linux-stable.git/log/?h=3Dlinux-4.14.y-next Would be interesting to compare with what you end up with. -- Thanks, Sasha=