From: Daniel Mack <daniel@zonque.org>
To: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Lad@roeck-us.net, Prabhakar <prabhakar.csengg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mikko Perttunen <mperttunen@nvidia.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits)
Date: Wed, 01 Apr 2015 08:13:39 +0200 [thread overview]
Message-ID: <551B8C93.8010204@zonque.org> (raw)
In-Reply-To: <551B5BDC.5060706@roeck-us.net>
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
next prev parent reply other threads:[~2015-04-01 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:02 linux-next: Tree for Mar 31 Stephen Rothwell
2015-03-31 16:16 ` linux-next: Tree for Mar 31 (build failures and culprits) Guenter Roeck
2015-03-31 23:07 ` Greg Kroah-Hartman
2015-03-31 23:24 ` Michael Ellerman
2015-04-01 2:18 ` Guenter Roeck
2015-04-01 3:01 ` Michael Ellerman
2015-04-01 3:13 ` Guenter Roeck
2015-03-31 23:42 ` Stephen Rothwell
2015-04-01 2:24 ` Guenter Roeck
2015-04-01 2:45 ` Guenter Roeck
2015-04-01 6:13 ` Daniel Mack [this message]
2015-04-01 2:17 ` Guenter Roeck
2015-04-01 8:08 ` Russell King - ARM Linux
2015-04-01 12:23 ` Guenter Roeck
2015-04-01 3:16 ` Max Filippov
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=551B8C93.8010204@zonque.org \
--to=daniel@zonque.org \
--cc=Lad@roeck-us.net \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mperttunen@nvidia.com \
--cc=prabhakar.csengg@gmail.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=treding@nvidia.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.