LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rob Herring <robherring2@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: Custom printk format specifier for device node
Date: Tue, 31 Mar 2015 22:07:32 -0700 [thread overview]
Message-ID: <1427864852.18175.53.camel@perches.com> (raw)
In-Reply-To: <20150401045231.70614C4082F@trevor.secretlab.ca>
On Tue, 2015-03-31 at 21:52 -0700, Grant Likely wrote:
> Thinking about this more, I'd like to suggest a different format that
> gives us a nice hack on the name that makes it easy to remember:
> '%pOF[...]'
> 'O' still means 'object', but it is also overloaded for Open Firmware.
> That still leaves %pO? for other object types. What do you think?
I think that's fine.
next prev parent reply other threads:[~2015-04-01 5:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
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
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
2015-04-01 4:52 ` Grant Likely
2015-04-01 5:07 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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 17:13 ` Rob Herring
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=1427864852.18175.53.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 \
--subject='Re: [PATCH] of: Custom printk format specifier for device node' \
/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
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).