From: Ingo Molnar <mingo@elte.hu>
To: Luca Barbieri <luca@luca-barbieri.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
a.p.zijlstra@chello.nl, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] x86-32: improve atomic64_t functions (v2)
Date: Fri, 26 Feb 2010 11:14:23 +0100 [thread overview]
Message-ID: <20100226101423.GA25641@elte.hu> (raw)
In-Reply-To: <ff13bc9a1002240156x27e28764mb6ba24da0b125d81@mail.gmail.com>
* Luca Barbieri <luca@luca-barbieri.com> wrote:
> > I wonder if I could ask you to recreate your patchset on top of the
> > x86/asm branch in the -tip tree.
>
> Done, resent.
FYI, it triggered build failures in -tip testing:
lib/atomic64_test.c: In function 'test_atomic64':
lib/atomic64_test.c:116: error: implicit declaration of function 'atomic64_dec_if_positive'
Ingo
next prev parent reply other threads:[~2010-02-26 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 17:26 [PATCH 0/5] x86-32: improve atomic64_t functions (v2) Luca Barbieri
2010-02-19 17:26 ` [PATCH 1/5] x86: add support for relative CALL and JMP in alternatives (v2) Luca Barbieri
2010-02-19 17:26 ` [PATCH 2/5] x86: add support for lock prefix " Luca Barbieri
2010-02-19 17:26 ` [PATCH 3/5] x86-32: allow UP/SMP lock replacement in cmpxchg64 (v2) Luca Barbieri
2010-02-19 17:26 ` [PATCH 4/5] lib: add self-test for atomic64_t Luca Barbieri
2010-02-19 17:26 ` [PATCH 5/5] x86-32: rewrite 32-bit atomic64 functions in assembly (v2) Luca Barbieri
2010-02-23 22:47 ` [PATCH 0/5] x86-32: improve atomic64_t functions (v2) H. Peter Anvin
2010-02-24 9:56 ` Luca Barbieri
2010-02-26 10:14 ` Ingo Molnar [this message]
2010-02-26 11:08 ` Luca Barbieri
2010-02-26 11:23 ` Luca Barbieri
2010-03-01 7:35 ` H. Peter Anvin
2010-03-01 8:49 ` Paul Mackerras
2010-03-01 17:16 ` Luca Barbieri
2010-03-01 17:31 ` Luca Barbieri
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=20100226101423.GA25641@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@luca-barbieri.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.