From: peter@hurleysoftware•com (Peter Hurley)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/4] of: DT quirks infrastructure
Date: Fri, 20 Feb 2015 08:23:47 -0500 [thread overview]
Message-ID: <54E73563.5070404@hurleysoftware.com> (raw)
In-Reply-To: <23825C6A-7FF1-4D06-8802-F6964F71B97C@konsulko.com>
On 02/19/2015 09:41 AM, Pantelis Antoniou wrote:
> Hi Frank,
>
>> On Feb 19, 2015, at 04:08 , Frank Rowand <frowand.list@gmail•com> wrote:
>>
>> On 2/18/2015 6:59 AM, Pantelis Antoniou wrote:
>>> Implement a method of applying DT quirks early in the boot sequence.
>>>
>>> A DT quirk is a subtree of the boot DT that can be applied to
>>> a target in the base DT resulting in a modification of the live
>>> tree. The format of the quirk nodes is that of a device tree overlay.
>>
>> The use of the word "quirk" is a different mental model for me than what
>> this patch series appears to be addressing. I would suggest totally
>> removing the word "quirk" from this proposal to avoid confusing the
>> mental models of future generations of kernel folks.
>>
>
> Naming things is hard to do. Suggestions?
variant
next prev parent reply other threads:[~2015-02-20 13:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 14:59 [PATCH 0/4] Device Tree Quirks & the Beaglebone Pantelis Antoniou
2015-02-18 14:59 ` [PATCH 1/4] arm: of: Add a DT quirk method after unflattening Pantelis Antoniou
2015-02-18 14:59 ` [PATCH 2/4] of: DT quirks infrastructure Pantelis Antoniou
2015-02-18 15:41 ` Mark Rutland
2015-02-18 15:53 ` Pantelis Antoniou
2015-02-18 16:32 ` Ludovic Desroches
2015-02-18 16:39 ` Pantelis Antoniou
2015-02-18 16:47 ` Ludovic Desroches
2015-02-18 16:46 ` Matt Porter
2015-02-18 17:31 ` Mark Rutland
2015-02-18 19:32 ` Guenter Roeck
2015-02-19 14:29 ` Pantelis Antoniou
2015-02-19 16:48 ` Frank Rowand
2015-02-19 17:00 ` Pantelis Antoniou
2015-02-19 17:30 ` Frank Rowand
2015-02-19 17:38 ` Pantelis Antoniou
2015-02-19 18:01 ` Maxime Bizon
2015-02-19 18:12 ` Sylvain Rochet
2015-02-19 18:22 ` Maxime Bizon
2015-02-20 14:21 ` Peter Hurley
2015-02-20 14:35 ` Ludovic Desroches
2015-02-20 15:00 ` Peter Hurley
2015-02-20 15:02 ` Pantelis Antoniou
2015-02-20 15:24 ` Peter Hurley
2015-02-20 15:38 ` Pantelis Antoniou
2015-02-20 16:34 ` Peter Hurley
2015-02-20 16:49 ` Pantelis Antoniou
2015-02-20 17:30 ` Rob Herring
2015-02-20 17:37 ` Pantelis Antoniou
2015-02-23 7:00 ` Ludovic Desroches
2015-02-20 14:38 ` Pantelis Antoniou
2015-02-20 16:47 ` Guenter Roeck
2015-02-20 18:09 ` Peter Hurley
2015-02-20 18:48 ` Guenter Roeck
2015-02-23 7:30 ` Ludovic Desroches
2015-02-20 8:04 ` Ludovic Desroches
2015-02-19 2:08 ` Frank Rowand
2015-02-19 14:41 ` Pantelis Antoniou
2015-02-19 16:40 ` Frank Rowand
2015-02-19 16:51 ` Frank Rowand
2015-02-20 13:23 ` Peter Hurley [this message]
2015-02-19 18:01 ` Rob Herring
2015-02-19 18:12 ` Guenter Roeck
2015-02-20 8:16 ` Ludovic Desroches
2015-02-18 14:59 ` [PATCH 3/4] arm: am33xx: DT quirks for am33xx based beaglebone variants Pantelis Antoniou
2015-02-19 18:16 ` Tony Lindgren
2015-02-19 18:28 ` Pantelis Antoniou
2015-02-19 18:36 ` Tony Lindgren
2015-02-19 18:44 ` Pantelis Antoniou
2015-02-23 18:39 ` Peter Hurley
2015-02-23 18:48 ` Pantelis Antoniou
2015-02-19 18:57 ` Guenter Roeck
2015-02-20 16:13 ` Jon Hunter
2015-02-18 14:59 ` [PATCH 4/4] arm: dts: Common Black/White Beaglebone DTS using quirks Pantelis Antoniou
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=54E73563.5070404@hurleysoftware.com \
--to=peter@hurleysoftware$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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