From: Pavel Machek <pavel@ucw.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
James Hogan <jhogan@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 10:01:42 +0200 [thread overview]
Message-ID: <20180404080142.GC9342@amd> (raw)
In-Reply-To: <CAMuHMdVZg8BL7D2eB-FnDbJabU3sfda6nOnaCdJj-3OC-+KP0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
On Tue 2018-04-03 11:18:15, Geert Uytterhoeven wrote:
> On Mon, Apr 2, 2018 at 9:54 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Mon, Apr 2, 2018 at 8:57 PM, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > Regarding a possible revert, that would indeed involve reverting
> > multiple patches for most architectures, plus parts of at least these
> > three:
> >
> > Documentation: arch-support: remove obsolete architectures
> > treewide: simplify Kconfig dependencies for removed archs
> > ktest: remove obsolete architectures
> >
> > For those, I went the other way, and removed all architectures at
> > once to simplify my work and to avoid touching the same files up
> > to eight times with interdependent patches (which couldn't
> > be reverted without conflicts either).
> >
> > There are a couple of driver removal patches that got picked up
> > into subsystem trees instead of this tree, so a full revert would also
> > involve finding other drivers, but if you prefer to have the patches
> > completely split up by arch, I could rework the series that way.
>
> In reality, a resurrection may not be implemented as a pure revert, but as
> the addition of a new architecture, implemented using modern features (DT,
> CCF, ...).
By insisting on new features instead of pure revert + incremental
updates, you pretty much make sure resurection will not be possible
:-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-04-04 8:01 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 [this message]
2018-04-04 8:38 ` Arnd Bergmann
2018-04-04 13:28 ` James Hogan
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=20180404080142.GC9342@amd \
--to=pavel@ucw.cz \
--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=jhogan@kernel.org \
--cc=lennox.wu@gmail.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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