From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>, Pavel Machek <pavel@ucw.cz>
Cc: devicetree@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: Consistent capitalization of "device tree"?
Date: Mon, 7 Jan 2019 17:09:40 -0800 [thread overview]
Message-ID: <4d4cf1b1-0966-305d-9bf3-e9dc84d6e8c6@gmail.com> (raw)
In-Reply-To: <CAL_JsqKzs4WoJoe_uCzhS3NBGfHiTQ96GkfSRhtxeah0THoVyw@mail.gmail.com>
On 1/7/19 10:45 AM, Rob Herring wrote:
> On Mon, Jan 7, 2019 at 12:37 PM Pavel Machek <pavel@ucw.cz> wrote:
>>
>> Is it "Device Tree" or "device tree"?
>>
>> pavel@duo:/data/l/k/Documentation$ grep -r "Device Tree" | wc -l
>> 235
>> pavel@duo:/data/l/k/Documentation$ grep -r "device tree" | wc -l
>> 595
>>
>> I guess it would be nice to make it consistent. I guess "device tree"
>> is preffered?
>
> Well, the spec uses "devicetree" with capital 'D' as needed (titles
> and start of sentences). I didn't check if we're 100% consistent
> there.
For reference, the specification is at:
https://www.devicetree.org/specifications/
>
>> Should we do something like this?
>
> I'll take patches, but it wouldn't be at the top of my list.
>
> Rob
>
next prev parent reply other threads:[~2019-01-08 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 18:37 Consistent capitalization of "device tree"? Pavel Machek
2019-01-07 18:44 ` Matthew Wilcox
2019-01-07 18:45 ` Rob Herring
2019-01-08 1:09 ` Frank Rowand [this message]
2019-01-07 19:06 ` Frank Rowand
2019-01-07 19:24 ` Pavel Machek
2019-01-08 4:49 ` Frank Rowand
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=4d4cf1b1-0966-305d-9bf3-e9dc84d6e8c6@gmail.com \
--to=frowand.list@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.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).