From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lichao Liu <liulichao@loongson.cn>
Cc: Paul Burton <paulburton@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Max Filippov <jcmvbkbc@gmail.com>,
jiaxun.yang@flygoat.com, yuanjunqing@loongson.cn,
linux-mips@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: CPU_LOONGSON2EF need software to maintain cache consistency
Date: Thu, 28 May 2020 09:44:48 +0200 [thread overview]
Message-ID: <20200528074448.GB10708@alpha.franken.de> (raw)
In-Reply-To: <20200528011031.30472-1-liulichao@loongson.cn>
On Thu, May 28, 2020 at 09:10:31AM +0800, Lichao Liu wrote:
> CPU_LOONGSON2EF need software to maintain cache consistency,
> so modify the 'cpu_needs_post_dma_flush' function to return true
> when the cpu type is CPU_LOONGSON2EF.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Lichao Liu <liulichao@loongson.cn>
> ---
> arch/mips/mm/dma-noncoherent.c | 1 +
> 1 file changed, 1 insertion(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-05-28 7:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:10 [PATCH] MIPS: CPU_LOONGSON2EF need software to maintain cache consistency Lichao Liu
2020-05-28 6:05 ` Jiaxun Yang
2020-05-28 7:44 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-26 11:14 Lichao Liu
2020-05-26 11:38 ` Jiaxun Yang
2020-05-26 12:40 ` Lichao Liu
2020-05-26 13:01 ` Thomas Bogendoerfer
2020-05-26 13:29 ` Robin Murphy
2020-05-26 15:01 ` Lichao Liu
2020-05-26 15:25 ` Jiaxun Yang
2020-05-26 16:00 ` Thomas Bogendoerfer
2020-05-26 16:42 ` Jiaxun Yang
2020-05-26 16:16 ` Thomas Bogendoerfer
2020-05-26 13:25 ` Jiaxun Yang
2020-05-26 14:50 ` Lichao Liu
2020-05-27 10:49 ` Thomas Bogendoerfer
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=20200528074448.GB10708@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=geert@linux-m68k.org \
--cc=jcmvbkbc@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=liulichao@loongson.cn \
--cc=paulburton@kernel.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=yuanjunqing@loongson.cn \
/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).