From: David Gibson <david@gibson.dropbear.id.au>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-mips <linux-mips@linux-mips.org>,
microblaze-uclinux@itee.uq.edu.au,
devicetree-discuss@lists.ozlabs.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
sparclinux@vger.kernel.org
Subject: Re: RFC: Mega rename of device tree routines from of_*() to dt_*()
Date: Mon, 29 Nov 2010 16:55:29 +1100 [thread overview]
Message-ID: <20101129055529.GB17113@yookeroo> (raw)
In-Reply-To: <1290692075.689.20.camel@concordia>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
On Fri, Nov 26, 2010 at 12:34:35AM +1100, Michael Ellerman wrote:
> On Thu, 2010-11-25 at 01:03 +1100, Michael Ellerman wrote:
> > Hi all,
> >
> > There were some murmurings on IRC last week about renaming the of_*()
> > routines.
> ...
> > The thinking is that on many platforms that use the of_() routines
> > OpenFirmware is not involved at all, this is true even on many powerpc
> > platforms. Also for folks who don't know the OpenFirmware connection
> > it reads as "of", as in "a can of worms".
> ...
> > So I'm hoping people with either say "YES this is a great idea", or "NO
> > this is stupid".
>
> I'm still hoping, but so far it seems most people have got better things
> to do, and of those that do have an opinion the balance is slightly
> positive.
>
> So here's a first cut of a patch to add the new names. I've not touched
> of_platform because that is supposed to go away. That will lead to some
> odd looking code in the interim, but I think is the right approach.
>
> Most of these are straight renames, but some have changed more
> substantially. The routines for the flat tree have all become fdt_foo().
I'm a little uneasy about using the same prefix as libfdt (fdt_foo())
for routines that have a different implementation and different names
/ semantics to the libfdt routines.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-29 5:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290607413.12457.44.camel@concordia>
2010-11-25 13:34 ` RFC: Mega rename of device tree routines from of_*() to dt_*() Michael Ellerman
2010-11-25 14:01 ` Geert Uytterhoeven
2010-11-25 20:52 ` Benjamin Herrenschmidt
2010-11-25 16:17 ` Grant Likely
2010-11-26 3:15 ` Michael Ellerman
2010-11-26 3:15 ` Michael Ellerman
2010-11-26 4:42 ` Mitch Bradley
2010-11-26 4:42 ` Mitch Bradley
[not found] ` <4CEF3AB1.9060200-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2010-11-26 5:50 ` Michael Ellerman
2010-11-26 5:50 ` Michael Ellerman
2010-11-26 7:15 ` Grant Likely
2010-11-26 7:36 ` Mitch Bradley
2010-11-26 7:36 ` Mitch Bradley
2010-11-29 5:55 ` David Gibson [this message]
2010-11-29 5:55 ` David Gibson
2010-11-29 6:07 ` Grant Likely
2010-11-29 6:07 ` Grant Likely
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=20101129055529.GB17113@yookeroo \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=sparclinux@vger.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