lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 8 Oct 2015 07:30:22 +0100
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Fengguang Wu <lkp@...el.com>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Lee Jones <lee.jones@...aro.org>, kbuild-all@...org,
	linux-kernel@...r.kernel.org
Subject: Re: [kbuild-all] [PATCH 2/2] mfd: rtsx: fix build warning

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ