[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551B8C93.8010204@zonque.org>
Date: Wed, 01 Apr 2015 08:13:39 +0200
From: Daniel Mack <daniel@...que.org>
To: Guenter Roeck <linux@...ck-us.net>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Tony Lindgren <tony@...mide.com>, Felipe Balbi <balbi@...com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Russell King <rmk+kernel@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>, Lad@...ck-us.net,
Prabhakar <prabhakar.csengg@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mikko Perttunen <mperttunen@...dia.com>,
Thierry Reding <treding@...dia.com>
Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits)
On 04/01/2015 04:45 AM, Guenter Roeck wrote:
> On 03/31/2015 07:24 PM, Guenter Roeck wrote:
>> Now I am left with the question if the samples build should be
>> masked for alpha and mips, or if I should drop building samples
>> from my 'allmodconfig' builds. I think I'll do the latter;
>> there seems to be an expectation that samples are built with
>> a recent toolchain, and I can not keep rebuilding toolchains for
>> the rest of my life.
>>
>
> Weird - the kdbus sample doesn't have its own configuration option,
> unlike other samples. So it's all or nothing for alpha and mips.
I've already sent a patch for this yesterday, and I'm sure Greg will
merge it anytime soon:
https://lkml.org/lkml/2015/3/31/306
I wouldn't mind if we masked that config symbol for archs which don't
have memfds wired, but I'm also open to other suggestions.
Thanks,
Daniel
--
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