Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: sync c-tx39.c with c-r4k.c
Date: Fri, 30 Sep 2005 00:30:58 +0100	[thread overview]
Message-ID: <20050929233058.GA3983@linux-mips.org> (raw)
In-Reply-To: <20050928.202458.32344678.nemoto@toshiba-tops.co.jp>

On Wed, Sep 28, 2005 at 08:24:58PM +0900, Atsushi Nemoto wrote:

> tx39_flush_cache_range() do nothing if !cpu_has_dc_aliases.  It should
> flush d-cache and invalidate i-cache since TX39(H2) has separate I/D
> cache.

Thanks, applied.

If you and other patch submitters would in the future please also start
sending patches with Signed-off-by: lines, for more please see
Documentation/SubmittingPatches.

In the past I didn't bother because we ended up blending all patches in
the CVS archive anyway to the point where they just didn't make sense
anymore.  Now with git that has changed.

  Ralf

      reply	other threads:[~2005-09-30 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 11:24 sync c-tx39.c with c-r4k.c Atsushi Nemoto
2005-09-29 23:30 ` 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=20050929233058.GA3983@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --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