mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Howells <dhowells@redhat.com>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Document Linux's memory barriers [try #6]
Date: Fri, 31 Mar 2006 16:22:04 +0100	[thread overview]
Message-ID: <7739.1143818524@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603301657410.4652-100000@iolanthe.rowland.org>

Alan Stern <stern@rowland.harvard.edu> wrote:

> I've got some comments inspired by the data-dependency sections of your
> memory-barrier document.

Thanks for that, but can you reconsider your comments in terms of the [try #7]
I've just released?  That stuff has changed a fair amount.

Cheers,
David

  reply	other threads:[~2006-03-31 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 22:01 Alan Stern
2006-03-31 15:22 ` David Howells [this message]
2006-03-31 21:01   ` [PATCH] Document Linux's memory barriers [try #7] Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23 20:01 [PATCH] Document Linux's memory barriers [try #6] 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=7739.1143818524@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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