From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Samium Gromoff <deepfire@sic-elvis.zel.ru>, linux-mips@linux-mips.org
Subject: Re: a shared cache_op() macros?
Date: Tue, 20 Jan 2004 16:56:07 +0300 [thread overview]
Message-ID: <87ektuvi4o.wl@canopus.ns.zel.ru> (raw)
In-Reply-To: <20040120134944.GA24044@linux-mips.org>
At Tue, 20 Jan 2004 14:49:44 +0100,
Ralf Baechle wrote:
>
> On Tue, Jan 20, 2004 at 04:42:46PM +0300, Samium Gromoff wrote:
>
> > While pondering for some generic mips cache initialisation routines, i
> > have found a precious cache_op() macro in mm/r5k-sc.c.
> >
> > And the question is, why isn`t it shared amongst all of the implementations
> > which could make use of it?
> >
> > regards, Samium Gromoff
>
> You're looking at an ancient tree; this has long been done.
Well, yes, it`s 2.4.20 :-)
> Ralf
regards, Samium Gromoff
prev parent reply other threads:[~2004-01-20 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hdyqvjh2.wl@canopus.ns.zel.ru>
2004-01-20 13:42 ` a shared cache_op() macros? Samium Gromoff
2004-01-20 13:49 ` Ralf Baechle
2004-01-20 13:56 ` Samium Gromoff [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=87ektuvi4o.wl@canopus.ns.zel.ru \
--to=deepfire@sic-elvis.zel.ru \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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