From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Huacai Chen <chenhc@lemote.com>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>,
Paul Burton <paul.burton@mips.com>
Subject: Re: [PATCH 0/5] MIPS: Loongson64: separate loongson2ef/loongson64 code
Date: Tue, 22 Oct 2019 10:47:20 +0800 [thread overview]
Message-ID: <B253D5C6-FA22-455A-8745-18A7D1E862B7@flygoat.com> (raw)
In-Reply-To: <CAAhV-H6iCHprEHRa2Do2QEQD+UkML=X=UwemR3OELXCrBhwv7w@mail.gmail.com>
于 2019年10月22日 GMT+08:00 上午9:35:38, Huacai Chen <chenhc@lemote.com> 写到:
>Hi, Jiaxun
>
>On Mon, Oct 21, 2019 at 11:56 AM Jiaxun Yang <jiaxun.yang@flygoat.com>
>wrote:
>>
>>
>>
>> 于 2019年10月21日 GMT+08:00 上午9:07:52, Huacai Chen <chenhc@lemote.com>
>写到:
>> >Hi, Jiaxun,
>> >
>> >Can we just "retire" the Loongson-2E/2F support? Let 5.4-lts be the
>> >last version which support Loongson-2E/2F.
>> Hi Huacai,
>>
>> There are still a lot of Loongson-2F users. Please don't leave them
>alone.
>>
>> I'm still going to maintain these code. Although might not be very
>active.
>If Loongson-2E/2F block us to modernize Loongson64, let's just retire
>it; if it doesn't block us, we don't need to separate.
Let's get separate merged and see what are we going to do next.
Loongson 2F is only about ten years old. Still very young to other MIPS machines lie in kernel tree.
>
>Huacai
>>
>>
>> >
>> >Huacai
>> >
>> --
>> Jiaxun Yang
--
Jiaxun Yang
prev parent reply other threads:[~2019-10-22 2:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 14:43 [PATCH 0/5] MIPS: Loongson64: separate loongson2ef/loongson64 code Jiaxun Yang
2019-10-20 14:43 ` [PATCH 1/6] MIPS: Loongson64: Rename CPU TYPES Jiaxun Yang
2019-11-01 23:27 ` Paul Burton
2019-10-20 14:43 ` [PATCH 2/6] MIPS: Fork loongson2ef from loongson64 Jiaxun Yang
2019-11-01 23:27 ` Paul Burton
2019-10-20 14:43 ` [PATCH 3/6] MIPS: Loongson2ef: clean up loongson64 related code Jiaxun Yang
2019-11-01 23:27 ` Paul Burton
2019-10-20 15:01 ` [PATCH 4/6] MIPS: Loongson64: Cleanup unused code Jiaxun Yang
2019-10-20 15:01 ` [PATCH 5/6] MIPS: Loongson64: Move files to the top-level directory Jiaxun Yang
2019-11-01 23:28 ` Paul Burton
2019-10-20 15:01 ` [PATCH 6/6] MAINTAINERS: Fix entries for Loongson2EF and add myself to Loongson64 Jiaxun Yang
2019-11-01 23:28 ` [PATCH 4/6] MIPS: Loongson64: Cleanup unused code Paul Burton
2019-10-21 1:07 ` [PATCH 0/5] MIPS: Loongson64: separate loongson2ef/loongson64 code Huacai Chen
2019-10-21 3:55 ` Jiaxun Yang
2019-10-22 1:35 ` Huacai Chen
2019-10-22 2:47 ` Jiaxun Yang [this message]
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=B253D5C6-FA22-455A-8745-18A7D1E862B7@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=chenhc@lemote.com \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.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).