From: Christoph Hellwig <hch@infradead.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
xfs-masters@oss.sgi.com,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-cris-kernel@axis.com
Subject: Re: Build regressions/improvements in v3.0-rc5 (xfs on cris)
Date: Wed, 29 Jun 2011 17:24:20 -0400 [thread overview]
Message-ID: <20110629212420.GA9822@infradead.org> (raw)
In-Reply-To: <20110629142106.447393a5.rdunlap@xenotime.net>
On Wed, Jun 29, 2011 at 02:21:06PM -0700, Randy Dunlap wrote:
> Looks like arch/cris does not support atomic64_t. (?)
>
> Should we prevent xfs from being built on arch/cris?
Or nuke cris until it's able to at least include an asm-generic header?
next prev parent reply other threads:[~2011-06-29 21:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 8:13 Build regressions/improvements in v3.0-rc5 Geert Uytterhoeven
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (arch/cris) Randy Dunlap
2011-06-30 8:23 ` Américo Wang
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (ssize_t ???) Randy Dunlap
2011-06-30 6:59 ` Geert Uytterhoeven
2011-06-30 7:16 ` Mikael Starvik
2011-06-30 8:01 ` Christoph Hellwig
2011-06-30 8:43 ` Geert Uytterhoeven
2011-06-30 8:56 ` Christoph Hellwig
2011-06-30 9:32 ` Geert Uytterhoeven
2011-06-30 9:44 ` Christoph Hellwig
2011-06-30 17:07 ` Andreas Schwab
2011-07-01 5:25 ` Mikael Starvik
2011-07-01 8:34 ` Andreas Schwab
2011-06-30 16:12 ` Randy Dunlap
2011-06-29 21:21 ` Build regressions/improvements in v3.0-rc5 (xfs on cris) Randy Dunlap
2011-06-29 21:24 ` Christoph Hellwig [this message]
2011-06-30 8:34 ` Américo Wang
2011-07-01 22:05 ` Build regressions/improvements in v3.0-rc5 Arnd Bergmann
2011-07-01 23:15 ` Mike Frysinger
2011-07-02 8:38 ` Arnd Bergmann
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=20110629212420.GA9822@infradead.org \
--to=hch@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox