From: Ben Elliston <bje@au.ibm.com>
To: sid@sources.redhat.com
Subject: Re: [patch] Better checking for cache line state
Date: Mon, 10 May 2004 23:15:00 -0000 [thread overview]
Message-ID: <s9r65b37u32.fsf@fs.ozlabs.ibm.com> (raw)
In-Reply-To: <200405102156.i4ALuNcU015081@pobox.toronto.redhat.com>
"Dave Brolley" <brolley@redhat.com> writes:
> On the target I'm working on, the programmer can directly write into
> the cache tags. This requires more vigilance regarding the state of
> the cache tags. Specifically, we should check the result of valid_p
> () before using the tag.
Looks good, Dave. Thanks,
Ben
prev parent reply other threads:[~2004-05-10 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 21:56 Dave Brolley
2004-05-10 23:15 ` Ben Elliston [this message]
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=s9r65b37u32.fsf@fs.ozlabs.ibm.com \
--to=bje@au.ibm.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).