From: yamada.masahiro@socionext.com (Masahiro Yamada)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: add "simple-bus" to "arm, amba-bus" compatible nodes
Date: Tue, 8 Mar 2016 14:54:54 +0900 [thread overview]
Message-ID: <CAK7LNASi381k5H3usDj1oLr=uzn7VTMS1jquSVaVEjd5JxWt_g@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLBNo2YuJGqBo1DaYgzV7=WuX-0BPutoW3f3U1k0wX3_w@mail.gmail.com>
Hi Rob, Mark, Jon,
Setting aside the future plan, anyway we should avoid
relying on an undocumented compatible string.
(and we should avoid its spread as Rob pointed out.)
I rephrase the git-log (no update in the code-diff).
Could you check v2, please?
https://patchwork.kernel.org/patch/8529701/
Better?
2016-03-04 5:23 GMT+09:00 Rob Herring <robh+dt@kernel.org>:
> On Thu, Mar 3, 2016 at 4:12 AM, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
>> On Thu, 2016-03-03 at 12:07 +0900, Masahiro Yamada wrote:
>> [...]
>>> This patch is derived from Rob Herring' comment
>>> "BTW, we should also kill off "amba-bus" which is an ambiguous term"
>>> in the following thread:
>>> http://lkml.iu.edu/hypermail/linux/kernel/1601.0/01822.html
>>>
>>>
>>> So, the plan would be like this:
>>>
>>> [1] Make device trees not depend on "arm,amba-bus" (this commit)
>>> [2] New device trees should no longer use "arm,amba-bus" alone.
>>> [3] Go though some releases until we do not care about the backward
>>> compatibility
>>
>> Why would we stop caring about backwards compatibility? If I was a user
>> of any of the platforms in question and updated my kernel, I wouldn't
>> expect to have to debug why it was broken, then install a new dtb to fix
>> it - which may be a tricky thing to do, depending on the firmware used
>> to boot Linux.
>
> If no one notices, then there is no ABI. Things break all the time
> when nobody cares. It will be more than a few releases for sure. We
> may never get to step 3, but we should do step 1 so people stop
> copy-n-pasting this in step 2.
>
> Rob
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-03-08 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 3:57 [PATCH] ARM: dts: add "simple-bus" to "arm, amba-bus" compatible nodes Masahiro Yamada
2016-03-01 11:46 ` [PATCH] ARM: dts: add "simple-bus" to "arm,amba-bus" " Mark Rutland
2016-03-03 3:07 ` [PATCH] ARM: dts: add "simple-bus" to "arm, amba-bus" " Masahiro Yamada
2016-03-03 10:12 ` Jon Medhurst (Tixy)
2016-03-03 20:23 ` Rob Herring
2016-03-08 5:54 ` Masahiro Yamada [this message]
2016-03-03 20:44 ` Rob Herring
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='CAK7LNASi381k5H3usDj1oLr=uzn7VTMS1jquSVaVEjd5JxWt_g@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--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).