From: Arnd Bergmann <arnd@arndb.de>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: 'Thomas Gleixner' <tglx@linutronix.de>,
'Paul Mundt' <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] unicore32 fix: remove arch-specific futex support
Date: Fri, 1 Apr 2011 11:09:23 +0200 [thread overview]
Message-ID: <201104011109.23966.arnd@arndb.de> (raw)
In-Reply-To: <004301cbef8c$b0bf0640$123d12c0$@mprc.pku.edu.cn>
On Thursday 31 March 2011, Guan Xuetao wrote:
> For cmpxchg, we have both system call and kuser_cmpxchg supports in old abi
> which are similar to arm.
> The performance of system call version is too poor, so it could be only used for test.
>
Let's forget about doing futex support for unicore32 then and use your original
patch.
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2011-04-01 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 8:48 [PATCH] unicore32 fix: remove arch-specific futex support Guan Xuetao
2011-03-30 12:17 ` Arnd Bergmann
2011-03-30 12:27 ` Thomas Gleixner
2011-03-30 12:40 ` Arnd Bergmann
2011-03-30 12:50 ` Thomas Gleixner
2011-03-31 10:16 ` Guan Xuetao
2011-04-01 9:09 ` Arnd Bergmann [this message]
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=201104011109.23966.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gxt@mprc.pku.edu.cn \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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