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 A05F08A5 for ; Mon, 1 Aug 2016 13:35:11 +0000 (UTC) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 68F072AE for ; Mon, 1 Aug 2016 13:35:11 +0000 (UTC) Date: Mon, 1 Aug 2016 21:35:05 +0800 From: Fengguang Wu To: Vinod Koul Message-ID: <20160801133505.GA19618@wfg-t540p.sh.intel.com> References: <20160725190125.GS5537@wotan.suse.de> <5486315.Z6uhQZYKqJ@avalon> <20160728205324.GB5642@wfg-t540p.sh.intel.com> <2443703.ScQNYO34Bz@avalon> <20160728230713.GB18980@wfg-t540p.sh.intel.com> <20160728233327.GC3296@wotan.suse.de> <20160729000912.GA17232@wfg-t540p.sh.intel.com> <20160730170556.GR3296@wotan.suse.de> <20160731063558.GA3493@wfg-t540p.sh.intel.com> <20160731173214.GO9681@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20160731173214.GO9681@localhost> Cc: Vegard Nossum , Wenzhong Sun , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Jul 31, 2016 at 11:02:15PM +0530, Vinod Koul wrote: >On Sun, Jul 31, 2016 at 02:35:58PM +0800, Fengguang Wu wrote: >> > >> >How about linux-next ? >> >> linux-next could be perfectly supported, however in a different >> "rebase" way than the "merges" for RC kernels. >> >> Suppose there are 100 branches based on -rc2 and another 100 branches >> on -rc3. We can typically merge most of the 200 branches onto -rc3, >> since there are relatively few changes between -rc2 and -rc3. > >Since linux-next already contains all maintainer branches slated for -next, >merging that won't help much and seems tedious. I think 0day should just >runs tests on top of linux-next everyday and report, if not done already. Yes we are already testing linux-next. There are some few trees based on linux-next because many LKML patches could be applied to it for testing -- if they cannot apply to "guessed" maintainer trees and RC kernels. So we have to handle patches on linux-next well. Thanks, Fengguang