From: "Segher Boessenkool" <segher@kernel.crashing.org>
To: "Matt Evans" <matt@ozlabs.org>
Cc: sarah.a.sharp@linux.intel.com, linuxppc-dev@ozlabs.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/5] xhci: Add rmb() between reading event validity & event data access.
Date: Sat, 26 Mar 2011 00:11:49 +0100 (CET) [thread overview]
Message-ID: <61164.94.211.195.167.1301094709.squirrel@gate.crashing.org> (raw)
In-Reply-To: <4D8C47CD.3020108@ozlabs.org>
> On weakly-ordered systems, the reading of an event's content must occur
> after reading the event's validity.
Put a comment on the rmb() saying what it orders?
Segher
next prev parent reply other threads:[~2011-03-25 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 7:44 [PATCH 3/5] xhci: Add rmb() between reading event validity & event data access Matt Evans
2011-03-25 23:11 ` Segher Boessenkool [this message]
2011-03-28 4:52 ` [PATCH v2 " Matt Evans
2011-03-28 22:20 ` Sarah Sharp
2011-03-29 18:56 ` Dmitry Torokhov
2011-03-29 21:23 ` Benjamin Herrenschmidt
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=61164.94.211.195.167.1301094709.squirrel@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@ozlabs.org \
--cc=sarah.a.sharp@linux.intel.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;
as well as URLs for NNTP newsgroup(s).