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 0EDFB9D7 for ; Wed, 9 May 2018 16:04:34 +0000 (UTC) Received: from mail-ot0-f195.google.com (mail-ot0-f195.google.com [74.125.82.195]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6C980F4 for ; Wed, 9 May 2018 16:04:32 +0000 (UTC) Received: by mail-ot0-f195.google.com with SMTP id l13-v6so40756740otk.9 for ; Wed, 09 May 2018 09:04:32 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180509204727.7ff38021@canb.auug.org.au> References: <20180502194632.GB18390@sasha-vm> <20180503020550.GP2714@sirena.org.uk> <20180503031000.GC29205@thunk.org> <0276fcda-0385-8f22-dbdb-e063f7ed8bbe@roeck-us.net> <20180503224217.GR2714@sirena.org.uk> <20180503230905.GA98604@atomide.com> <20180509084440.GW13402@sirena.org.uk> <20180509090346.GY13402@sirena.org.uk> <20180509204727.7ff38021@canb.auug.org.au> From: Dan Williams Date: Wed, 9 May 2018 09:04:31 -0700 Message-ID: To: Stephen Rothwell Content-Type: text/plain; charset="UTF-8" Cc: "ksummit-discuss@lists.linuxfoundation.org" , linux-nvdimm , Greg KH , "linux-kernel@vger.kernel.org" , "w@1wt.eu" Subject: Re: [Ksummit-discuss] bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, May 9, 2018 at 3:47 AM, Stephen Rothwell wrote: > On Wed, 9 May 2018 18:03:46 +0900 Mark Brown wrote: >> >> On Wed, May 09, 2018 at 10:47:57AM +0200, Daniel Vetter wrote: >> > On Wed, May 9, 2018 at 10:44 AM, Mark Brown wrote: >> >> > > I think this is an excellent idea, copying in Stephen for his input. >> > > I'm currently on holiday but unless someone convinces me it's a terrible >> > > idea I'm willing to at least give it a go on a trial basis once I'm back >> > > home. >> >> > Since Stephen merges all -fixes branches first, before merging all the >> > -next branches, he already generates that as part of linux-next. All >> > he'd need to do is push that intermediate state out to some >> > linux-fixes branch for consumption by test bots. > > Good idea ... I will see what I can do. > >> True. It's currently only those -fixes branches that people have asked >> him to merge separately which isn't as big a proportion of trees as have >> them (perhaps fortunately given people's enthusiasm for fixes branches >> that don't merge cleanly with their development branches) so we'd also >> need to encourage people to add them separately. > > I currently have 44 such fixes branches. More welcome! Please add: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git libnvdimm-fixes We currently merge this into libnvdimm-for-next for -next coverage, and resolve any conflicts vs new development. Do you want to see those conflicts? Otherwise I would recommend only pulling libnvdimm-for-next for -next and libnvdimm-fixes for this new -next-fixes effort.