From: Arnd Bergmann <arnd@arndb.de>
To: David Miller <davem@davemloft.net>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: comedi doesn't build on several architectures
Date: Wed, 22 Jun 2011 16:08:59 +0200 [thread overview]
Message-ID: <201106221608.59978.arnd@arndb.de> (raw)
In-Reply-To: <20110621.194925.1313933193955144936.davem@davemloft.net>
On Wednesday 22 June 2011, David Miller wrote:
> It depends upon PAGE_KERNEL_NOCACHE which only a handful of
> platforms define.
>
> Really, enabling staging in Linus's tree with all this build fallout
> was not the wisest. It's blowing up all of my allmodconfig test
> builds now.
Is staging supposed to compile on non-x86? I've done a lot of
ARM randconfig builds, but I just disabled all of staging using
KCONFIG_ALLCONFIG because I didn't see the point.
Arnd
next prev parent reply other threads:[~2011-06-22 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 2:49 comedi doesn't build on several architectures David Miller
2011-06-22 3:16 ` Stephen Rothwell
2011-06-22 14:08 ` Arnd Bergmann [this message]
2011-06-22 15:39 ` Greg KH
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=201106221608.59978.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox