From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752724AbbJHGa0 (ORCPT ); Thu, 8 Oct 2015 02:30:26 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:39311 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752233AbbJHGaZ (ORCPT ); Thu, 8 Oct 2015 02:30:25 -0400 Date: Thu, 8 Oct 2015 07:30:22 +0100 From: Greg KH To: Fengguang Wu Cc: Sudip Mukherjee , Lee Jones , kbuild-all@01.org, linux-kernel@vger.kernel.org Subject: Re: [kbuild-all] [PATCH 2/2] mfd: rtsx: fix build warning Message-ID: <20151008063022.GA23343@kroah.com> References: <1444220929-18949-2-git-send-email-sudipm.mukherjee@gmail.com> <201510072007.NVdfT1ah%fengguang.wu@intel.com> <20151007124652.GA19200@sudip-pc> <20151007134816.GB15834@wfg-t540p.sh.intel.com> <20151007154125.GA20077@sudip-pc> <20151008005638.GA23669@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151008005638.GA23669@wfg-t540p.sh.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 08, 2015 at 08:56:38AM +0800, Fengguang Wu wrote: > On Wed, Oct 07, 2015 at 09:11:25PM +0530, Sudip Mukherjee wrote: > > On Wed, Oct 07, 2015 at 09:48:16PM +0800, Fengguang Wu wrote: > > > On Wed, Oct 07, 2015 at 06:16:52PM +0530, Sudip Mukherjee wrote: > > > > On Wed, Oct 07, 2015 at 08:40:37PM +0800, kbuild test robot wrote: > > > > > Hi Sudip, > > > > > > > > > > [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore] > > > > v4.3-rc4 is not appropriate base. Please use next-20151007 for both. > > > > > > OK. FYI, if you use [PATCH (next|-next|linux-next)] next time, > > > the robot will select linux-next/master as the base tree. > > Ok. Great. And for staging should it be [PATCH staging-testing] ? > > It looks some patches already use the form [PATCH staging], I wonder > which branch Greg typically apply them to, staging-testing or staging-next? I start by putting things in staging-testing to "test" them on my systems, and yours, and if they survive, I then move them to -next. staging-testing can be rebased if there is problems, but -next can not, which is why I do this. hope this helps, greg k-h