From: David Woodhouse <dwmw2@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Chris Wedgwood <cw@f00f.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
bjornw@axis.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org
Subject: Re: Missing cache flush.
Date: Tue, 05 Jun 2001 13:42:50 +0100 [thread overview]
Message-ID: <14071.991744970@redhat.com> (raw)
In-Reply-To: <15132.41562.879696.484467@pizda.ninka.net>
davem@redhat.com said:
> David Woodhouse writes:
> > What shall we call this function? The intuitive "flush_dcache_range"
> > appears to have already been taken.
> Call it flush_ecache_full() or something.
Strange name. Why? How about __flush_cache_range()?
--
dwmw2
next prev parent reply other threads:[~2001-06-05 12:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 23:16 Missing cache flush David Woodhouse
2001-06-04 23:23 ` Jeff Garzik
2001-06-04 23:29 ` David Woodhouse
2001-06-05 2:04 ` David S. Miller
2001-06-05 2:03 ` David S. Miller
[not found] ` <20010605155550.C22741@metastasis.f00f.org>
2001-06-05 4:01 ` David S. Miller
2001-06-05 8:46 ` David Woodhouse
2001-06-05 8:50 ` David S. Miller
2001-06-05 9:05 ` David Woodhouse
2001-06-05 9:11 ` David S. Miller
2001-06-05 12:42 ` David Woodhouse [this message]
2001-06-05 12:48 ` David S. Miller
2001-06-05 12:52 ` David Woodhouse
2001-06-06 8:32 ` Albert D. Cahalan
2001-06-06 19:48 ` Pavel Machek
2001-06-05 17:01 ` Jamie Lokier
2001-06-05 9:29 ` kira brown
2001-06-05 17:16 ` Alan Cox
2001-06-06 19:44 ` Earyly Cyrix CPUs was " Pavel Machek
2001-06-08 16:00 ` Alan Cox
2001-06-05 9:43 ` Johan Adolfsson
2001-06-05 9:17 ` Bjorn Wesen
2001-06-05 14:22 ` Vipin Malik
[not found] ` <20010606005703.A23758@metastasis.f00f.org>
2001-06-05 15:17 ` Ralf Baechle
[not found] <20010606112419.A24800@metastasis.f00f.org>
2001-06-06 8:43 ` James Sutherland
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=14071.991744970@redhat.com \
--to=dwmw2@infradead.org \
--cc=bjornw@axis.com \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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