From: Joe Perches <joe@perches.com>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Rob Herring <robherring2@gmail.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>
Subject: Re: [PATCH] of: Custom printk format specifier for device node
Date: Tue, 20 Jan 2015 09:59:54 -0800 [thread overview]
Message-ID: <1421776794.2724.1.camel@perches.com> (raw)
In-Reply-To: <E7065DB3-DD6B-4110-A066-8C7268186831@konsulko.com>
On Tue, 2015-01-20 at 16:52 +0200, Pantelis Antoniou wrote:
> Hi Rob,
>
> > On Jan 20, 2015, at 16:47 , Rob Herring <robherring2@gmail.com> wrote:
> >
> > On Tue, Jan 20, 2015 at 8:34 AM, Pantelis Antoniou
> > <pantelis.antoniou@konsulko.com> wrote:
> >> 90% of the usage of device node's full_name is printing it out
> >> in a kernel message. Preparing for the eventual delayed allocation
> >> introduce a custom printk format specifier that is both more
> >> compact and more pleasant to the eye.
[]
> >> diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
[]
> >> +Device tree nodes:
> >> +
> >> + %pO{,1,2}
> >
> > 'O' is not very obvious, but I imagine we are somewhat limted in our
> > choice here?
> >
>
> All the good women are married, all the handsome men are gay, all the obvious
> format specifiers are taken.
Not really at all.
I quite dislike '0' as the format type specifier for
a device tree node as there's no mnemonic mapping.
next prev parent reply other threads:[~2015-01-20 17:59 UTC|newest]
Thread overview: 30+ 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:34 ` Pantelis Antoniou
2015-01-20 14:47 ` Rob Herring
2015-01-20 14:52 ` Pantelis Antoniou
2015-01-20 17:59 ` Joe Perches [this message]
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:06 ` Pantelis Antoniou
2015-01-20 18:16 ` Joe Perches
2015-01-20 15:24 ` Geert Uytterhoeven
2015-01-20 15:27 ` Pantelis Antoniou
2015-01-20 16:05 ` Måns Rullgård
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-21 17:59 ` Måns Rullgård
2015-01-22 20:31 ` Pantelis Antoniou
2015-03-30 19:04 ` Grant Likely
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: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 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=1421776794.2724.1.camel@perches.com \
--to=joe@perches.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.