From: James Hogan <jhogan@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
"moderated list:PANASONIC MN10300..."
<linux-am33-list@redhat.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Lennox Wu <lennox.wu@gmail.com>, Aaron Wu <Aaron.Wu@analog.com>,
Bryan Wu <cooloney@gmail.com>,
Chris Metcalf <chris.d.metcalf@gmail.com>,
Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [GIT PULL] arch: remove obsolete architecture ports
Date: Wed, 4 Apr 2018 14:28:16 +0100 [thread overview]
Message-ID: <20180404132815.GC25517@saruman> (raw)
In-Reply-To: <CAK8P3a3Rj7utFTrNrNiv3948whE9Tsta9mmLPdX5HxBhif-_9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On Wed, Apr 04, 2018 at 10:38:41AM +0200, Arnd Bergmann wrote:
> Also, now that the other architectures are gone, a lot of changes can
> be done more easily that will be incompatible with a pure revert, so
> the more time passes, the harder it will get to do that.
Yes, and an out-of-tree arch port (as effectively these arches now are)
requires constant maintenance (often subtle runtime breakage) to keep up
to date with each new kernel release, which happens mostly automatically
from arch maintainer POV while they're merged.
Even without changes intentionally taking advantage of not having to
care about these arches, it'll be only a few cycles at the most before a
plain revert won't "just work".
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-04 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 7:17 [GIT PULL] arch: remove obsolete architecture ports Arnd Bergmann
2018-04-02 18:57 ` Linus Torvalds
2018-04-02 19:54 ` Arnd Bergmann
2018-04-03 9:18 ` Geert Uytterhoeven
2018-04-04 8:01 ` Pavel Machek
2018-04-04 8:38 ` Arnd Bergmann
2018-04-04 13:28 ` James Hogan [this message]
2018-04-03 2:57 ` Palmer Dabbelt
2018-04-03 4:08 ` Linus Torvalds
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=20180404132815.GC25517@saruman \
--to=jhogan@kernel.org \
--cc=Aaron.Wu@analog.com \
--cc=arnd@arndb.de \
--cc=chris.d.metcalf@gmail.com \
--cc=cooloney@gmail.com \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jesper.nilsson@axis.com \
--cc=lennox.wu@gmail.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=takata@linux-m32r.org \
--cc=torvalds@linux-foundation.org \
/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