All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Huacai Chen <chenhc@lemote.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	Paul Burton <paul.burton@mips.com>,
	linux-mips@linux-mips.org, linux-mips@vger.kernel.org,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>,
	Huacai Chen <chenhuacai@gmail.com>
Subject: Re: [PATCH 1/3] MIPS: Loongson: Remove Loongson-2E/2F support
Date: Sun, 3 Nov 2019 23:08:26 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1911032301160.367459@eddie.linux-mips.org> (raw)
In-Reply-To: <1572758417-29265-1-git-send-email-chenhc@lemote.com>

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?

  Maciej

  parent reply	other threads:[~2019-11-03 23: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 ` Maciej W. Rozycki [this message]
2019-11-04  6:05   ` [PATCH 1/3] MIPS: Loongson: Remove Loongson-2E/2F support 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

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=alpine.LFD.2.21.1911032301160.367459@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=chenhc@lemote.com \
    --cc=chenhuacai@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@vger.kernel.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 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.