From: Fengguang Wu <fengguang.wu@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-janitors@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [userns:userns-always-map-user-v45 80/99] fs/namespace.c:2290:1: error: unknown type name 'atomi
Date: Mon, 13 Aug 2012 18:13:43 +0000 [thread overview]
Message-ID: <20120813181343.GA2055@localhost> (raw)
In-Reply-To: <20120813175516.GA32757@localhost>
On Tue, Aug 14, 2012 at 01:55:16AM +0800, Fengguang Wu wrote:
> > >I'd suggest to fix it in m68k and make atomic64_t generally available.
> >
> > Fengguang in your testing on any architechtures is atomic64_t missing on anything except some m68k subarchtechtures?
>
> Eric, it only complaints for m68k, among the architechtures the build
> tests covered (alpha arm avr32 blackfin cris frv h8300 i386 ia64 m32r
> m68k mips mn10300 openrisc parisc powerpc s390 sh sparc sparc64 tile
> um x86_64 xtensa).
Sorry, I must missed something (in my system, build errors are only
recorded on first sight)..
wfg /c/linux% for arch in arch/*/; do grep -ir -q atomic64 $arch || echo $arch; done
arch/c6x/
arch/h8300/
arch/mn10300/
arch/score/
arch/unicore32/
So the above archs are likely still missing atomic64_t support.
However it should be trivial to add support to them, by adding
"select GENERIC_ATOMIC64" lines to them.
Thanks,
Fengguang
next prev parent reply other threads:[~2012-08-13 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 14:50 [userns:userns-always-map-user-v45 80/99] fs/namespace.c:2290:1: error: unknown type name 'atomic64_ Fengguang Wu
2012-08-13 6:56 ` [userns:userns-always-map-user-v45 80/99] fs/namespace.c:2290:1: error: unknown type name 'atomi Eric W. Biederman
2012-08-13 13:39 ` Fengguang Wu
2012-08-13 16:13 ` Eric W. Biederman
2012-08-13 17:55 ` Fengguang Wu
2012-08-13 18:13 ` Fengguang Wu [this message]
2012-08-13 19:08 ` Architectures missing atomic64_t Eric W. Biederman
2012-08-14 14:57 ` Fengguang Wu
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=20120813181343.GA2055@localhost \
--to=fengguang.wu@intel.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).