From: Huacai Chen <chenhc@lemote.com>
To: "Maciej W. Rozycki" <macro@linux-mips.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: Mon, 4 Nov 2019 14:05:49 +0800 [thread overview]
Message-ID: <CAAhV-H7R3Ci+Z1kMc2MXcK69JwoH5+bxvGGCjrLzBNbEki76zg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1911032301160.367459@eddie.linux-mips.org>
Hi, Maciej,
On Mon, Nov 4, 2019 at 7:08 AM Maciej W. Rozycki <macro@linux-mips.org> wrote:
>
> On Sun, 3 Nov 2019, 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.
>
> People still use them, e.g. I do, and upstream removal causes an issue
> with the need to backport changes not specific to the platform.
>
> If you don't want to maintain the code, then just mark it orphan and rely
> on the community to maintain it. If it starts breaking and nobody picks
> it to make fixes, then it can be removed. There's no need to rush IMO.
>
> BTW, there used to be a patch somewhere to support more than 512MiB of
> DRAM with the 2E, but I can't find it -- can you help me tracking it down?
>
OK, we will keep Loongson-2E/2F in kernel for sometime, thanks.
Huacai
> Maciej
next prev parent reply other threads:[~2019-11-04 6:00 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 [this message]
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
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-H7R3Ci+Z1kMc2MXcK69JwoH5+bxvGGCjrLzBNbEki76zg@mail.gmail.com \
--to=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=paul.burton@mips.com \
--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).