From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: "tjin@wavecomp.com" <tjin@wavecomp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: MIPS Cache Coherency Issue
Date: Mon, 5 Aug 2019 21:13:29 +0000 [thread overview]
Message-ID: <1565039609.15175.3.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <MWHPR2201MB1119058430642AC300B621ACB8DA0@MWHPR2201MB1119.namprd22.prod.outlook.com>
On Mon, 2019-08-05 at 14:02 +0000, Tommy Jin wrote:
> Hi Chris,
>
> My name is Tommy, from wave computing Co,Ltd, our team is working on
> the maintenance of the MIPS kernel.
>
> You raised a MIPS cache coherency patch which can be found in the
> following links
> https://lore.kernel.org/linux-mips/20190528221255.22460-1-chris.packh
> am@alliedtelesis.co.nz/T/#u
>
> With Paul's patch, It seems you still get "other bad behaviour", it
> doesn't work for you. Has this issue been resolved?
In short no it hasn't been resolved. I haven't been able to spend much
time looking at the issue(s) so I haven't been able to tell if Paul's
patch uncovered pre-existing issues or caused new ones.
Unfortunately I probably won't get onto it any time soon. I was hoping
to get some of my other team members to pick up the issue but they're
all busy as well.
next parent reply other threads:[~2019-08-05 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MWHPR2201MB1119058430642AC300B621ACB8DA0@MWHPR2201MB1119.namprd22.prod.outlook.com>
2019-08-05 21:13 ` Chris Packham [this message]
[not found] ` <MWHPR2201MB1119ECD5E55C8E1A9CFD3942B8D50@MWHPR2201MB1119.namprd22.prod.outlook.com>
2019-08-09 4:26 ` [EXTERNAL]Re: MIPS Cache Coherency Issue Chris Packham
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=1565039609.15175.3.camel@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tjin@wavecomp.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;
as well as URLs for NNTP newsgroup(s).