Re: [kbuild-all] [PATCH 2/2] mfd: rtsx: fix build warning

[Sudip Mukherjee <sudipm.mukherjee@gmail.com>]

On Thu, Oct 08, 2015 at 07:30:22AM +0100, Greg KH wrote:
> 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.

HI Fengguang,
I have a question for you. My build system is mostly based on your
make.cross file, which I have modified again to suit my build system in
travis-ci. But for some arch the compilers used by make.cross are really
old and it generated gcc bug while compiling. I faced them for two arch
in recent past. Current one is for cris. I was ablr to find out which
commit was responsible for that build fail but since its old gcc version
no one is interested. How do you handle that? Is there no way to get the
latest compilers to test with?

regards
sudip