From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Markos Chandras <markos.chandras@imgtec.com>,
<linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [4.1,013/123] MIPS: c-r4k: Fix cache flushing for MT cores
Date: Mon, 10 Aug 2015 12:12:05 -0700 [thread overview]
Message-ID: <55C8F785.5020605@imgtec.com> (raw)
In-Reply-To: <20150810184953.GA19646@kroah.com>
On 08/10/2015 11:49 AM, gregkh@linuxfoundation.org wrote:
> On Mon, Aug 10, 2015 at 11:36:34AM -0700, Leonid Yegoshin wrote:
>>
> So, this is broken in Linus's tree too?
Yes.
> Or is it fixed there, and if
> so, what is the git commit id?
There is no an accepted fix. My old patch is in
https://git.linux-mips.org/cgit/yegoshin/mips.git/commit/?id=98f6c462eb5319a4dcb3830f902c48141f38cd12
It was a precursor for my EVA set of patches since2.6.35.9 but was never
accepted and was lost during redesign of EVA by Markos.
- Leonid.
WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Markos Chandras <markos.chandras@imgtec.com>,
linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [4.1,013/123] MIPS: c-r4k: Fix cache flushing for MT cores
Date: Mon, 10 Aug 2015 12:12:05 -0700 [thread overview]
Message-ID: <55C8F785.5020605@imgtec.com> (raw)
Message-ID: <20150810191205.hMGftPPDuAhE0Q23zFRWrfCcJ2g41rZUma6MAo7AVF4@z> (raw)
In-Reply-To: <20150810184953.GA19646@kroah.com>
On 08/10/2015 11:49 AM, gregkh@linuxfoundation.org wrote:
> On Mon, Aug 10, 2015 at 11:36:34AM -0700, Leonid Yegoshin wrote:
>>
> So, this is broken in Linus's tree too?
Yes.
> Or is it fixed there, and if
> so, what is the git commit id?
There is no an accepted fix. My old patch is in
https://git.linux-mips.org/cgit/yegoshin/mips.git/commit/?id=98f6c462eb5319a4dcb3830f902c48141f38cd12
It was a precursor for my EVA set of patches since2.6.35.9 but was never
accepted and was lost during redesign of EVA by Markos.
- Leonid.
next prev parent reply other threads:[~2015-08-10 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150808220717.771230091@linuxfoundation.org>
2015-08-08 22:08 ` [PATCH 4.1 012/123] MIPS: Fix erroneous JR emulation for MIPS R6 Greg Kroah-Hartman
2015-08-08 22:08 ` [PATCH 4.1 013/123] MIPS: c-r4k: Fix cache flushing for MT cores Greg Kroah-Hartman
2015-08-10 18:36 ` [4.1,013/123] " Leonid Yegoshin
2015-08-10 18:36 ` Leonid Yegoshin
2015-08-10 18:49 ` gregkh
2015-08-10 19:12 ` Leonid Yegoshin [this message]
2015-08-10 19:12 ` Leonid Yegoshin
2015-08-10 19:17 ` Markos Chandras
2015-08-10 19:17 ` Markos Chandras
2015-08-10 19:19 ` gregkh
2015-08-10 19:22 ` Leonid Yegoshin
2015-08-10 19:22 ` Leonid Yegoshin
2015-08-08 22:08 ` [PATCH 4.1 014/123] MIPS: Require O32 FP64 support for MIPS64 with O32 compat Greg Kroah-Hartman
2015-08-08 22:08 ` [PATCH 4.1 015/123] MIPS: fpu.h: Allow 64-bit FPU on a 64-bit MIPS R6 CPU Greg Kroah-Hartman
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=55C8F785.5020605@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=stable@vger.kernel.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