From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Steven J. Hill" <sjhill@mips.com>,
linux-mips@linux-mips.org, Douglas Leung <douglas@mips.com>
Subject: Re: [PATCH] MIPS: Add support for the MIPS32 4Kc family I/D caches.
Date: Tue, 29 May 2012 09:48:31 +0100 [thread overview]
Message-ID: <20120529084831.GC9944@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1205270312110.3701@eddie.linux-mips.org>
On Sun, May 27, 2012 at 03:19:47AM +0100, Maciej W. Rozycki wrote:
> It was not a bug, or at least not an active one. The new encoding was
> only added with revision 3 of the architecture or thereabouts, so not so
> long ago. It used to be reserved previously, so we just handled it
> arbitrarily (though perhaps we should have panicked instead on
> encountering it indeed).
The patch at least was applicable to all 2.4 and 2.6 branches ...
Ralf
next prev parent reply other threads:[~2012-05-29 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:33 [PATCH] MIPS: Add support for the MIPS32 4Kc family I/D caches Steven J. Hill
2012-05-22 17:32 ` Ralf Baechle
2012-05-27 2:19 ` Maciej W. Rozycki
2012-05-29 8:48 ` Ralf Baechle [this message]
2012-05-29 10:48 ` Maciej W. Rozycki
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=20120529084831.GC9944@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=douglas@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=sjhill@mips.com \
/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