From: csd@broadcom.com (Christian Daudt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: DT: binding fixup to align with vendor-prefixes.txt
Date: Tue, 6 Aug 2013 14:40:20 -0700 [thread overview]
Message-ID: <52016D44.7060808@broadcom.com> (raw)
In-Reply-To: <520079DB.5090309@wwwdotorg.org>
On 13-08-05 09:21 PM, Stephen Warren wrote:
>>>> Required root node property:
>>>> -compatible = "bcm,bcm11351";
>>>> +compatible = "brcm,bcm11351";
>>> In a patch of mine that deprecated a property, Mark wondered if it would
>>> make sense to mention the old deprecated DT content simply to document
>>> that it existed, so that old DTs would still make sense when checking
>>> the documentation. I wonder if the same argument applies to this patch?
>> I would think the opposite. Deprecated items should be dropped from
>> documentation. They are in the code (for a holdover period) but clearly
>> marked as deprecated. No one should be extending the life of these, and
>> adding documentation on it is a step in the wrong direction of making it
>> easier for it to linger beyond what it should.
> The deprecated stuff will have to be fully documented once the DT schema
> validation is in place...
>
This deprecated code should be short lived, given that in actual fact it
is actually quite unnecessary since no boards exist that rely on it.
thanks,
csd
next prev parent reply other threads:[~2013-08-06 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 22:27 [PATCH v2] ARM: DT: binding fixup to align with vendor-prefixes.txt Christian Daudt
2013-08-05 16:01 ` Stephen Warren
2013-08-06 0:16 ` Christian Daudt
2013-08-06 4:21 ` Stephen Warren
2013-08-06 21:40 ` Christian Daudt [this message]
2013-08-09 16:11 ` Stephen Warren
[not found] ` <CAA-5wcDOv+ru+4QiDbEZr-SP90xHSh1bq+ifdVxOsOnid1komg@mail.gmail.com>
2013-08-09 18:49 ` Christian Daudt
2013-08-09 19:14 ` Stephen Warren
2013-08-10 19:56 ` Christian Daudt
2013-08-08 22:56 ` Christian Daudt
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=52016D44.7060808@broadcom.com \
--to=csd@broadcom.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).