Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] blast_scache nop for sc cpus without scache
Date: Sat, 25 Jun 2005 18:03:16 +0200	[thread overview]
Message-ID: <20050625160316.GP6953@linux-mips.org> (raw)
In-Reply-To: <20050625131938.GA7669@paradigm.rfc822.org>

On Sat, Jun 25, 2005 at 03:19:38PM +0200, Florian Lohoff wrote:

> Subject: [patch] blast_scache nop for sc cpus without scache

Interesting.  Which system needs this patch?

  Ralf

  reply	other threads:[~2005-06-25 16:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25 13:19 [patch] blast_scache nop for sc cpus without scache Florian Lohoff
2005-06-25 16:03 ` Ralf Baechle [this message]
2005-06-25 17:50   ` Thomas Bogendoerfer
2005-06-27 12:45     ` Maciej W. Rozycki
2005-06-27 14:36       ` Ralf Baechle
2005-06-27 15:31         ` Maciej W. Rozycki
2005-06-27 19:09       ` Thomas Bogendoerfer
2005-06-27 19:43         ` Maciej W. Rozycki
2005-06-28  7:20           ` peter fuerst
2005-06-28  9:11             ` Maciej W. Rozycki
2005-06-28  9:35               ` Stanislaw Skowronek

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=20050625160316.GP6953@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@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