From: Ingo Molnar <mingo@elte.hu>
To: Kyle McMartin <kyle@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
ralf@linux-mips.org, mingo@redhat.com
Subject: Re: x86: spinlocks: define dummy __raw_spin_is_contended
Date: Mon, 9 Feb 2009 10:44:40 +0100 [thread overview]
Message-ID: <20090209094440.GA13942@elte.hu> (raw)
In-Reply-To: <20090209092221.GG31890@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * Kyle McMartin <kyle@infradead.org> wrote:
>
> > CC-ing Linus, since he just released 2.6.29-rc4, which will fail to
> > build btrfs on anything besides mips or x86.
>
> Hm, i'm not particularly fond of the spin_is_contended() trickery done in:
having said that, Kyle's patch is obviously correct nevertheless - the above
is not to be taken as an objection.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2009-02-09 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 18:03 x86: spinlocks: define dummy __raw_spin_is_contended Kyle McMartin
2009-02-08 22:39 ` Kyle McMartin
2009-02-09 9:22 ` Ingo Molnar
2009-02-09 9:44 ` Ingo Molnar [this message]
2009-02-08 23:51 ` Ralf Baechle
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=20090209094440.GA13942@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=kyle@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--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