From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Andrew Morton <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH] of: Custom printk format specifier for device node
Date: Tue, 20 Jan 2015 16:24:00 +0100 [thread overview]
Message-ID: <CAMuHMdWnjawtgkKGuL8b4A17EhDS6B0L-1_uhSnvEXXk5dNjwQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLVJjq3Ov=J-5LtXiTQPLvR5Y=+tB1i16k_rN3j5dODFQ@mail.gmail.com>
On Tue, Jan 20, 2015 at 3:47 PM, Rob Herring <robherring2@gmail.com> wrote:
>> + Examples:
>> +
>> + %pO /foo/bar@0 - Node full name
>> + %pO0 /foo/bar@0 - Same as above
>> + %pO1 /foo/bar@0[10] - Node full name + phandle
>> + %pO2 /foo/bar@0[10:DdPB] - Node full name + phandle + node flags
>> + D - dynamic
>> + d - detached
>> + P - Populated
>> + B - Populated bus
>
> We should think about what else we want to print for a node. Perhaps
> 'On' for name, 'Oc' for compatible, etc.
I was just going to say "The least verbose variant is name, not full_name".
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-01-20 15:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 14:34 [PATCH] of: Custom printk format specifier for device node Pantelis Antoniou
2015-01-20 14:47 ` Rob Herring
2015-01-20 14:52 ` Pantelis Antoniou
2015-01-20 17:59 ` Joe Perches
2015-01-20 18:03 ` Rob Herring
[not found] ` <1421776794.2724.1.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-01-20 18:06 ` Pantelis Antoniou
2015-01-20 18:16 ` Joe Perches
2015-01-20 15:24 ` Geert Uytterhoeven [this message]
2015-01-20 15:27 ` Pantelis Antoniou
2015-01-20 16:05 ` Måns Rullgård
2015-01-20 17:13 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2015-01-21 17:06 Pantelis Antoniou
2015-01-21 17:37 ` Joe Perches
2015-01-21 17:39 ` Pantelis Antoniou
2015-01-21 17:52 ` Joe Perches
[not found] ` <D84576D1-27F5-44F9-83DA-347C26F593FE-wVdstyuyKrO8r51toPun2/C9HSW9iNxf@public.gmane.org>
2015-01-21 17:59 ` Måns Rullgård
2015-01-22 20:31 ` Pantelis Antoniou
2015-03-30 19:04 ` Grant Likely
2015-03-31 10:03 ` Pantelis Antoniou
2015-03-31 17:02 ` Grant Likely
2015-03-31 17:14 ` Pantelis Antoniou
[not found] ` <8421E7C5-C0D9-4C86-AA37-F6507B3BCC57-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-01 4:52 ` Grant Likely
2015-04-01 5:07 ` Joe Perches
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=CAMuHMdWnjawtgkKGuL8b4A17EhDS6B0L-1_uhSnvEXXk5dNjwQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=rdunlap@infradead.org \
--cc=robherring2@gmail.com \
/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).