From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] x86/spinlocks optional for 3.1
Date: Mon, 01 Aug 2011 18:02:22 -0700 [thread overview]
Message-ID: <4E374C9E.5000102@zytor.com> (raw)
In-Reply-To: <CA+55aFyKFP3KzVfSEO02TjjmMDDL5agCJjKERFdmStM4k9DtQQ@mail.gmail.com>
On 08/01/2011 05:04 PM, Linus Torvalds wrote:
>
> If that xadd implementation could perhaps be shared, I wouldn't hate
> it so much. As it is, I really don't see the point in pulling this.
>
OK, no problem. We'll rework it for 3.2.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2011-08-02 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 17:53 [GIT PULL] x86/spinlocks optional for 3.1 H. Peter Anvin
2011-08-02 0:04 ` Linus Torvalds
2011-08-02 1:02 ` H. Peter Anvin [this message]
2011-08-02 17:02 ` Jeremy Fitzhardinge
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=4E374C9E.5000102@zytor.com \
--to=hpa@zytor.com \
--cc=hpa@linux.intel.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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