From: Greg KH <gregkh@linuxfoundation.org>
To: Fengguang Wu <lkp@intel.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] [PATCH 2/2] mfd: rtsx: fix build warning
Date: Thu, 8 Oct 2015 07:30:22 +0100 [thread overview]
Message-ID: <20151008063022.GA23343@kroah.com> (raw)
In-Reply-To: <20151008005638.GA23669@wfg-t540p.sh.intel.com>
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
next prev parent reply other threads:[~2015-10-08 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 12:28 [PATCH 1/2] mfd: lm3533: fix build warning Sudip Mukherjee
2015-10-07 12:28 ` [PATCH 2/2] mfd: rtsx: " Sudip Mukherjee
2015-10-07 12:40 ` kbuild test robot
2015-10-07 12:46 ` Sudip Mukherjee
2015-10-07 13:48 ` [kbuild-all] " Fengguang Wu
2015-10-07 15:41 ` Sudip Mukherjee
2015-10-08 0:56 ` Fengguang Wu
2015-10-08 6:30 ` Greg KH [this message]
2015-10-08 7:45 ` Sudip Mukherjee
2015-10-13 8:45 ` Lee Jones
2015-10-07 12:41 ` [PATCH 1/2] mfd: lm3533: " kbuild test robot
2015-10-13 8:45 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151008063022.GA23343@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sudipm.mukherjee@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.