From: Huacai Chen <chenhc@lemote.com>
To: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Paul Burton <paul.burton@mips.com>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>
Subject: Re: [PATCH 1/3] MIPS: Loongson: Remove Loongson-2E/2F support
Date: Tue, 5 Nov 2019 09:14:22 +0800 [thread overview]
Message-ID: <CAAhV-H4tzoPu_iHh9aUVRtwmNsJTQLkOJRN2i2159m_L7m1YRQ@mail.gmail.com> (raw)
In-Reply-To: <20191104190330.hpzuqsyh5j5tkr4p@lantea.localdomain>
Hi, Paul
On Tue, Nov 5, 2019 at 3:03 AM Paul Burton <paulburton@kernel.org> wrote:
>
> Hi Huacai,
>
> On Sun, Nov 03, 2019 at 01:20:15PM +0800, Huacai Chen wrote:
> > Loongson-2E/2F is old, inactive and a bit ugly, so let's remove them
> > and the world will be more comfortable.
> >
> > Old:
> > Products with Loongson-2E/2F are more than ten years old, there is no
> > new products.
> >
> > Inactive:
> > There are not any updates for a long time, and the maintainer (Jiaxun
> > Yang) focuses on Loongson-3 now.
>
> Jiaxun just made changes to the 2E/2F code just a couple of weeks ago to
> separate it from other Loongson64 support & clean it up - he also
> indicated at the same time that he intends to contiue maintaining this
> code [1].
>
> > Ugly:
> > Loongson-2E/2F are not compatible with regular MIPS, e.g., ebase, cache
> > flush method and tlb refill handler.
>
> Sadly "quirks" like this aren't solely the domain of Loongson 2E/2F
> machines, so this isn't an unusual burden.
>
> > Linux-5.4.x is a LTS release, I think it is the suitable time to remove
> > Loongson-2E/2F.
>
> I disagree - Jiaxun says he's happy to maintain the platform & has
> recently been working on it. I'm not going to remove it & deny him that
> chance. If it does indeed become unmaintained then sure let's drop it,
> but that doesn't seem to be the case here.
>
OK, I will keep Loongson-2E/2F in the kernel, and please review my
other patches. Thanks.
Huacai
> Thanks,
> Paul
>
> [1] https://lore.kernel.org/linux-mips/AF48876C-308C-46AD-B7B4-77BFA2413EDE@flygoat.com/
prev parent reply other threads:[~2019-11-05 1:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1572758417-29265-1-git-send-email-chenhc@lemote.com>
2019-11-03 5:20 ` [PATCH 2/3] MIPS: Loongson: Rename LOONGSON1 to LOONGSON32 Huacai Chen
2019-11-03 11:26 ` Huacai Chen
2019-11-03 5:20 ` [PATCH 3/3] MIPS: Loongson: Unify LOONGSON3/LOONGSON64 Kconfig usage Huacai Chen
2019-11-03 5:35 ` Jiaxun Yang
2019-11-03 23:08 ` [PATCH 1/3] MIPS: Loongson: Remove Loongson-2E/2F support Maciej W. Rozycki
2019-11-04 6:05 ` Huacai Chen
2019-11-05 13:54 ` Jiaxun Yang
2020-02-26 2:38 ` Maciej W. Rozycki
2019-11-04 19:03 ` Paul Burton
2019-11-05 1:14 ` Huacai Chen [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=CAAhV-H4tzoPu_iHh9aUVRtwmNsJTQLkOJRN2i2159m_L7m1YRQ@mail.gmail.com \
--to=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--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 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).