mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Scott Preece" <sepreece@gmail.com>
To: "Jarek Poplawski" <jarkao2@o2.pl>
Cc: "David Howells" <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org,
	"Robert P. J. Day" <rpjday@mindspring.com>
Subject: Re: [PATCH] Documentation/memory-barriers.txt: various fixes
Date: Tue, 22 May 2007 08:39:25 -0500	[thread overview]
Message-ID: <7b69d1470705220639w767eda81g5d4988ef09d77316@mail.gmail.com> (raw)
In-Reply-To: <20070521151953.GC4050@ff.dom.local>

On 5/21/07, Jarek Poplawski <jarkao2@o2.pl> wrote:
> On Mon, May 21, 2007 at 03:12:07PM +0100, David Howells wrote:
> > Jarek Poplawski <jarkao2@o2.pl> wrote:
> >
> > > > > -     load will be directed), a data dependency barrier would be required to
> > > > > +     load will be directed), the data dependency barrier would be required to
> > > >
> > > > I think that should be "a".
> > >
> > > I could only guess (it's a magic to me) - so, if it doesn't matter
> > > "A data ..." begins this paragraph...
> >
> > I see what you mean.  I see it as "a data dependency barrier ..." though.  That
> > may be because I wrote the doc, however.  I wonder if "data dependency" should
> > be hyphenated to make it clearer.  What do you think?
>
> Better don't ask. Now I'm far less decided, than yesterday.
---

"data-dependency barrier" would be better, assuming you mean a barrier
enforcing a data dependency. If you say "data dependency barrier" you
could also mean a "dependency barrier" implemented as a piece of data,
for instance, like a flag value in a data stream that forces
synchronization with another data stream.

scott

  reply	other threads:[~2007-05-22 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  9:42 Jarek Poplawski
2007-05-21 12:09 ` David Howells
2007-05-21 13:50   ` Jarek Poplawski
2007-05-21 14:12   ` David Howells
2007-05-21 15:19     ` Jarek Poplawski
2007-05-22 13:39       ` Scott Preece [this message]
2007-05-22 14:19         ` Jarek Poplawski
2007-05-22  6:19     ` [PATCH (take 2)] " Jarek Poplawski
2007-05-22 12:16     ` David Howells
2007-05-22 13:35     ` [PATCH (take 3)] " Jarek Poplawski
2007-05-22 13:43       ` Jarek Poplawski
2007-05-22 14:03     ` [PATCH (take 4)] " Jarek Poplawski
2007-05-22 15:56     ` David Howells

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=7b69d1470705220639w767eda81g5d4988ef09d77316@mail.gmail.com \
    --to=sepreece@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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

all inboxes | Powered by JetHome®