From: David Daney <ddaney@caviumnetworks.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Matt Redfearn <matt.redfearn@imgtec.com>,
linux-mmc@vger.kernel.org, david.daney@cavium.com,
ulf.hansson@linaro.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Zubair.Kakakhel@imgtec.com,
Aleksey Makarov <aleksey.makarov@caviumnetworks.com>,
Chandrakala Chavva <cchavva@caviumnetworks.com>,
Aleksey Makarov <aleksey.makarov@auriga.com>,
Leonid Rosenboim <lrosenboim@caviumnetworks.com>,
Peter Swain <pswain@cavium.com>,
Aaron Williams <aaron.williams@cavium.com>
Subject: Re: [PATCH v5] mmc: OCTEON: Add host driver for OCTEON MMC controller
Date: Wed, 10 Feb 2016 16:32:45 -0800 [thread overview]
Message-ID: <56BBD6AD.2090902@caviumnetworks.com> (raw)
In-Reply-To: <20160210234907.GC1640@darkstar.musicnaut.iki.fi>
On 02/10/2016 03:49 PM, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Feb 10, 2016 at 10:02:23AM -0800, David Daney wrote:
>> On 02/10/2016 09:36 AM, Matt Redfearn wrote:
>>> + pr_warn(FW_WARN "%s: Legacy property '%s'. Please remove\n",
>>> + node->full_name, legacy_name);
>>
>> I don't like this warning message.
>>
>> The vast majority of people that see it will not be able to change their
>> firmware. So it will be forever cluttering up their boot logs.
>
> Until they switch to use APPENDED_DTB. :-)
>
I am philosophically opposed to making the DTB an internal kernel
implementation detail.
For OCTEON boards, it is an ABI between the boot firmware and the
kernel, and is impractical to change.
One could argue that many years ago, when the decision was made (by me),
that we should have opted to carry in the kernel source code tree the
DTS files for all OCTEON boards ever made, but we did not do that. Due
to the non-reversibility of time, the decision is hard to reverse.
In the case of this MMC driver, the only real difference is that two
properties have legacy names that later had differing "official" names.
The overhead of carrying the legacy bindings is very low.
David.
next prev parent reply other threads:[~2016-02-11 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:36 [PATCH v5] mmc: OCTEON: Add host driver for OCTEON MMC controller Matt Redfearn
2016-02-10 18:02 ` David Daney
[not found] ` <56BB7B2F.60307-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-02-10 23:49 ` Aaro Koskinen
2016-02-11 0:32 ` David Daney [this message]
2016-02-11 2:55 ` Florian Fainelli
[not found] ` <56BBF83B.8020908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-11 8:15 ` Matt Redfearn
[not found] ` <56BBD6AD.2090902-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-02-11 19:28 ` Maciej W. Rozycki
2016-02-11 8:12 ` Matt Redfearn
2016-02-10 19:01 ` Ulf Hansson
[not found] ` <CAPDyKFrMgt9snP2NLbQ6EQ5X7gjQLA+e+TEfqgjzLYTuH+G1OA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-10 20:07 ` David Daney
2016-02-11 8:24 ` Matt Redfearn
2016-02-11 9:12 ` Ulf Hansson
2016-02-11 16:17 ` David Daney
2016-02-12 15:39 ` Rob Herring
2016-02-15 8:11 ` Matt Redfearn
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=56BBD6AD.2090902@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=aaro.koskinen@iki.fi \
--cc=aaron.williams@cavium.com \
--cc=aleksey.makarov@auriga.com \
--cc=aleksey.makarov@caviumnetworks.com \
--cc=cchavva@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrosenboim@caviumnetworks.com \
--cc=matt.redfearn@imgtec.com \
--cc=pswain@cavium.com \
--cc=ulf.hansson@linaro.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).