From: "Måns Rullgård" <mans@mansr.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
"Maciej W. Rozycki" <macro@imgtec.com>,
David Daney <ddaney@caviumnetworks.com>,
James Hogan <james.hogan@imgtec.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] mips: Fix arch_spin_unlock()
Date: Tue, 02 Feb 2016 15:51:17 +0000 [thread overview]
Message-ID: <yw1xh9hri00a.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <20160202145817.GB30875@linux-mips.org> (Ralf Baechle's message of "Tue, 2 Feb 2016 15:58:18 +0100")
Ralf Baechle <ralf@linux-mips.org> writes:
> On Tue, Feb 02, 2016 at 02:54:06PM +0000, Måns Rullgård wrote:
>
>> We don't really have much choice given the reality of existing hardware.
>
> No, of course not - but I want us discourage new weakly ordered
> platforms as much as possible.
Where do you draw the line though? You can't exactly go and impose some
kind of global ordering in a multi-master system.
--
Måns Rullgård
next prev parent reply other threads:[~2016-02-02 15:51 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 12:31 Peter Zijlstra
2015-11-12 12:35 ` Peter Zijlstra
2015-11-12 13:31 ` Måns Rullgård
2015-11-12 14:32 ` Paul E. McKenney
2015-11-12 14:50 ` Måns Rullgård
2015-11-12 14:59 ` Paul E. McKenney
2015-11-12 17:46 ` David Daney
2015-11-12 18:00 ` Peter Zijlstra
2015-11-12 18:13 ` Måns Rullgård
2015-11-12 18:17 ` David Daney
2016-01-27 9:57 ` Maciej W. Rozycki
2016-01-27 11:43 ` Will Deacon
2016-01-27 12:41 ` Maciej W. Rozycki
2016-01-28 1:11 ` Boqun Feng
2016-01-27 14:54 ` Peter Zijlstra
2016-01-27 15:21 ` Will Deacon
2016-01-27 23:38 ` Paul E. McKenney
2016-01-28 9:57 ` Will Deacon
2016-01-28 22:31 ` Paul E. McKenney
2016-01-29 9:59 ` Will Deacon
2016-01-29 10:22 ` Paul E. McKenney
2016-02-01 13:56 ` Will Deacon
2016-02-02 3:54 ` Paul E. McKenney
2016-02-02 5:19 ` Boqun Feng
2016-02-02 6:44 ` Paul E. McKenney
2016-02-02 8:07 ` Linus Torvalds
2016-02-02 8:19 ` Linus Torvalds
2016-02-02 9:34 ` Boqun Feng
2016-02-02 17:30 ` Linus Torvalds
2016-02-02 17:51 ` Will Deacon
2016-02-02 18:06 ` Linus Torvalds
2016-02-02 19:30 ` Will Deacon
2016-02-02 19:55 ` Linus Torvalds
2016-02-03 19:13 ` Will Deacon
2016-02-03 8:33 ` Ingo Molnar
2016-02-03 13:32 ` Will Deacon
2016-02-03 19:03 ` Will Deacon
2016-02-09 11:23 ` Ingo Molnar
2016-02-09 11:42 ` Will Deacon
2016-02-02 12:02 ` Paul E. McKenney
2016-02-02 17:56 ` Linus Torvalds
2016-02-02 22:30 ` Paul E. McKenney
2016-02-02 14:49 ` Ralf Baechle
2016-02-02 14:54 ` Måns Rullgård
2016-02-02 14:58 ` Ralf Baechle
2016-02-02 15:51 ` Måns Rullgård [this message]
2016-02-02 17:23 ` Peter Zijlstra
2016-02-02 22:38 ` Paul E. McKenney
2016-02-02 11:45 ` Will Deacon
2016-02-02 12:12 ` Boqun Feng
2016-02-02 12:20 ` Will Deacon
2016-02-02 13:18 ` Boqun Feng
2016-02-02 17:12 ` Paul E. McKenney
2016-02-02 17:37 ` Will Deacon
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=yw1xh9hri00a.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=boqun.feng@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@imgtec.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome