From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Thomas Horsten <thomas@horsten.com>, linux-mips@linux-mips.org
Subject: Re: [BUG] R5000 failure in kmap_coherent on Lasat board, bug that has been there for a while?
Date: Fri, 13 Jun 2008 10:09:49 -0700 [thread overview]
Message-ID: <4852A9DD.6000602@avtrex.com> (raw)
In-Reply-To: <20080613165607.GB29015@linux-mips.org>
Ralf Baechle wrote:
> On Fri, Jun 13, 2008 at 09:53:03AM -0700, David Daney wrote:
>>>
>> I will try said patch on my O2/R5000 and the sigma8634.
>
> The patch is total bullshit. It doesn't even try to fix the issues but
> rather disables the alias-avoidance mechanism.
>
Upon further consideration of the patch, I tend to agree. It would be nice to fix the bug though.
David Daney
next prev parent reply other threads:[~2008-06-13 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 15:06 [BUG] R5000 failure in kmap_coherent on Lasat board, bug that has been there for a while? Thomas Horsten
2008-06-13 15:34 ` Ralf Baechle
2008-06-13 16:53 ` David Daney
2008-06-13 16:56 ` Ralf Baechle
2008-06-13 17:09 ` David Daney [this message]
2008-06-14 12:59 ` Ralf Baechle
2008-06-14 21:08 ` Thomas Horsten
2008-06-14 21:11 ` Ralf Baechle
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=4852A9DD.6000602@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=thomas@horsten.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