From: Alan Stern <stern@rowland.harvard.edu>
To: David Brownell <david-b@pacbell.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Nicolas DET <nd@bplan-gmbh.de>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-mm@kvack.org
Subject: Re: [linux-usb-devel] Patch for UHCI driver (from kernel 2.6.6).
Date: Tue, 15 Jun 2004 17:12:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0406151710070.658-100000@ida.rowland.org> (raw)
In-Reply-To: <40CF5D1B.6000302@pacbell.net>
On Tue, 15 Jun 2004, David Brownell wrote:
> > ... a write by either the device or the processor
> > can immediately be read by the processor or device
> > without having to worry about caching effects.
> >
> > This means that when you read _the data that was written_ you don't have
> > to worry about caching effects.
>
> It doesn't limit the "without having to worry" to just the bytes
> written.
It's hard to say exactly what it means because it's ungrammatical. "A
write ... can immediately be read..." -- what does it mean to read a
write?
> And the rest of that API spec doesn't even suggest that
> there might be an issue there. I think you're trying to read
> things into that text that aren't there.
Maybe so. It's not worth spending more time on this point, anyhow.
Alan Stern
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-06-15 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40CE2E24.5060207@pacbell.net>
2004-06-15 16:35 ` Alan Stern
2004-06-15 17:08 ` David Brownell
2004-06-15 17:23 ` Duncan Sands
2004-06-15 19:35 ` Alan Stern
2004-06-15 20:33 ` David Brownell
2004-06-15 21:12 ` Alan Stern [this message]
2004-06-15 21:40 ` Guennadi Liakhovetski
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=Pine.LNX.4.44L0.0406151710070.658-100000@ida.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david-b@pacbell.net \
--cc=linux-mm@kvack.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nd@bplan-gmbh.de \
/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