From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <rob.herring@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>, Icenowy Zheng <icenowy@aosc.xyz>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH] arm64: dts: allwinner: a64: Re-add "syscon" compatible
Date: Fri, 21 Sep 2018 17:16:25 +0200 [thread overview]
Message-ID: <20180921151625.wkaypyueyi2pguur@flea> (raw)
In-Reply-To: <20180921153522.0413c280@donnerap.Emea.Arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]
On Fri, Sep 21, 2018 at 03:35:22PM +0100, Andre Przywara wrote:
> The problem is: we broke compatibility with older kernels.
The problem is that we never said we wouldn't.
We've had this discussion a number of times. You forced the backward
compatibility onto us without any warning, and now we have to support
it. And it's already a pain. Maybe ARM can fix that problem by just
assigning more engineers to that, but that's not something we can do.
The fundamental difference is that we're mostly just a bunch of spare
time programmers working on this platform, with a partial
documentation for the controllers, at best.
You forced me to ask these developpers to work on their weekends and
evenings on some crazy corner cases to maintain the backward
compatibility. And honestly, both from a technical and human
standpoint, I definitely understand if some of them are just leaving
and don't want to work on it anymore. I would probably do the same in
their position.
And having to ask that for companies like ARM or SUSE just makes it
more frustrating to be honest. So there's simply no way you have
forward compatibility while I'm there. Or you manage to convince all
the ARM maintainers and enforce that compatibility for all the
platforms.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-09-21 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 15:28 [PATCH] arm64: dts: allwinner: a64: Re-add "syscon" compatible Andre Przywara
2018-09-21 9:47 ` Chen-Yu Tsai
2018-09-21 14:35 ` Andre Przywara
2018-09-21 14:57 ` Chen-Yu Tsai
2018-10-01 0:52 ` André Przywara
2018-09-21 15:16 ` Maxime Ripard [this message]
2018-09-24 10:22 ` Andre Przywara
2018-09-26 9:52 ` Maxime Ripard
2018-10-01 0:55 ` André Przywara
2018-10-04 15:02 ` Maxime Ripard
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=20180921151625.wkaypyueyi2pguur@flea \
--to=maxime.ripard@bootlin.com \
--cc=andre.przywara@arm.com \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@linaro.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).