From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: uniphier: drop code for old DT binding
Date: Tue, 31 May 2016 11:21:37 +0200 [thread overview]
Message-ID: <4992506.m4GEHIOqdc@wuerfel> (raw)
In-Reply-To: <1464682628-12163-1-git-send-email-yamada.masahiro@socionext.com>
On Tuesday, May 31, 2016 5:17:08 PM CEST Masahiro Yamada wrote:
> Commit 307d40c56b0c ("ARM: uniphier: rework SMP code to support new
> System Bus binding") added a new DT binding for SMP code, but still
> kept old code for the backward compatibility.
>
> Linux 4.6 was out with both bindings supported, so it should not
> hurt to drop the old code now.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>
That explanation is in general not sufficient. Are you sure that
nobody is shipping a machine with their own dts file that is not
merged upstream, and that there are no bootloaders that have a
hardcoded dtb file that we need to support indefinitely?
Arnd
next prev parent reply other threads:[~2016-05-31 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:17 [PATCH] ARM: uniphier: drop code for old DT binding Masahiro Yamada
2016-05-31 9:21 ` Arnd Bergmann [this message]
2016-06-01 6:30 ` Masahiro Yamada
2016-06-01 7:49 ` Arnd Bergmann
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=4992506.m4GEHIOqdc@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).