Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] c-r3k: Implement flush_cache_range()
Date: Mon, 29 Oct 2007 18:36:52 +0000	[thread overview]
Message-ID: <20071029183652.GF3953@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710171144410.28993@blysk.ds.pg.gda.pl>

On Wed, Oct 17, 2007 at 11:51:39AM +0100, Maciej W. Rozycki wrote:

>  Contrary to the belief of some, the R3000 and related processors did have 
> caches, both a data and an instruction cache.  Here is an implementation 
> of r3k_flush_cache_page(), which is the processor-specific back-end for 
> flush_cache_range(), done according to the spec in 
> Documentation/cachetlb.txt.
> 
>  While at it, remove an unused local function: get_phys_page(), do some 
> trivial formatting fixes and modernise debugging facilities.

Applied.

  Ralf

      reply	other threads:[~2007-10-29 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 10:51 [PATCH] c-r3k: Implement flush_cache_range() Maciej W. Rozycki
2007-10-29 18:36 ` Ralf Baechle [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=20071029183652.GF3953@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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