LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre.Peiffer@bull.net
Cc: mingo@elte.hu, drepper@redhat.com, linux-kernel@vger.kernel.org,
jean-pierre.dion@bull.net,
Pierre Peiffer <pierre.peiffer@bull.net>
Subject: Re: [PATCH 2.6.21-rc4-mm1 4/4] sys_futex64 : allows 64bit futexes
Date: Mon, 26 Mar 2007 03:20:23 -0800 [thread overview]
Message-ID: <20070326032023.0aa5ca7f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070321100542.438317770@bull.net>
On Wed, 21 Mar 2007 10:54:36 +0100 Pierre.Peiffer@bull.net wrote:
> It does not provide the functionality for all architectures (only for x64 for now).
Well that scuppers our chances of getting -mm kernels tested on ia64, s390
and sparc64. Which is a problem - people do test s390 and ia64 and so these
patches impact the testing quality of everyone else's work.
Do we have a plan to fix this (promptly, please)?
kernel/built-in.o(.text+0x683a2): In function `futex_requeue_pi':
: undefined reference to `futex_atomic_cmpxchg_inatomic64'
next prev parent reply other threads:[~2007-03-26 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 9:54 [PATCH 2.6.21-rc4-mm1 0/4] Futexes functionalities and improvements Pierre.Peiffer
2007-03-21 9:54 ` [PATCH 2.6.21-rc4-mm1 1/4] futex priority based wakeup Pierre.Peiffer
2007-03-21 9:54 ` [PATCH 2.6.21-rc4-mm1 2/4] Make futex_wait() use an hrtimer for timeout Pierre.Peiffer
2007-03-26 9:57 ` Andrew Morton
2007-03-21 9:54 ` [PATCH 2.6.21-rc4-mm1 3/4] futex_requeue_pi optimization Pierre.Peiffer
2007-03-21 9:54 ` [PATCH 2.6.21-rc4-mm1 4/4] sys_futex64 : allows 64bit futexes Pierre.Peiffer
2007-03-26 11:20 ` Andrew Morton [this message]
2007-03-27 11:07 ` Jakub Jelinek
2007-04-23 14:35 ` [PATCH -mm] 64bit-futex - provide new commands instead of new syscall Pierre Peiffer
2007-04-23 15:30 ` Ulrich Drepper
2007-04-24 8:07 ` [PATCH -mm take2] " Pierre Peiffer
2007-04-24 13:25 ` Ulrich Drepper
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=20070326032023.0aa5ca7f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Pierre.Peiffer@bull.net \
--cc=drepper@redhat.com \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).