All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Huacai Chen <chenhc@lemote.com>,
	linux-mips@vger.kernel.org, Fuxin Zhang <zhangfx@lemote.com>,
	Huacai Chen <chenhuacai@gmail.com>
Subject: Re: [PATCH V7 2/3] MIPS: Loongson-3: Enable COP2 usage in kernel
Date: Thu, 24 Sep 2020 15:53:53 +0200	[thread overview]
Message-ID: <20200924135353.GB13973@alpha.franken.de> (raw)
In-Reply-To: <177ADF0C-1633-449F-B589-712EA4857E79@flygoat.com>

On Wed, Sep 23, 2020 at 05:44:02PM +0800, Jiaxun Yang wrote:
> 于 2020年9月21日 GMT+08:00 下午8:15:54, Thomas Bogendoerfer <tsbogend@alpha.franken.de> 写到:
> >thanks for doing this, I'm going to apply this later.
> >
> >This remind of another question, what about loongson2ef ? I'm getting
> >kbuild failure because of enabled loongson-mmi mails. Are we are missing
> >something like cflags-y += $(call cc-option,-mno-loongson-mmi) in Platform
> >file ? Who is taking care of loongson2ef ?
> 
> I'll send a patch later. Sorry for the inconvenience.

excellent, thank you.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2020-09-24 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  9:12 [PATCH V7 1/3] MIPS: context switch: Use save/restore instead of set/clear for Status.CU2 Huacai Chen
2020-09-21  9:12 ` [PATCH V7 2/3] MIPS: Loongson-3: Enable COP2 usage in kernel Huacai Chen
2020-09-21 12:15   ` Thomas Bogendoerfer
2020-09-23  9:44     ` Jiaxun Yang
2020-09-24 13:53       ` Thomas Bogendoerfer [this message]
2020-09-21  9:12 ` [PATCH V7 3/3] MIPS: Loongson-3: Calculate ra properly when unwinding the stack Huacai Chen
2020-09-21 20:24 ` [PATCH V7 1/3] MIPS: context switch: Use save/restore instead of set/clear for Status.CU2 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=20200924135353.GB13973@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=chenhc@lemote.com \
    --cc=chenhuacai@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.