linux-kernel - RE: Mega rename of device tree routines from of_*() to dt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ee487d0b-ec9d-42a9-9c8e-39f83858cffc@SG2EHSMHS007.ehs.local>
Date:	Wed, 24 Nov 2010 10:32:11 -0800
From:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>
To:	David Daney <ddaney@...iumnetworks.com>
CC:	<michael@...erman.id.au>, LKML <linux-kernel@...r.kernel.org>,
	linux-mips <linux-mips@...ux-mips.org>,
	<microblaze-uclinux@...e.uq.edu.au>,
	<devicetree-discuss@...ts.ozlabs.org>,
	linuxppc-dev list <linuxppc-dev@...abs.org>,
	<sparclinux@...r.kernel.org>
Subject: RE: Mega rename of device tree routines from of_*() to dt_*()



> -----Original Message-----
> From: David Daney [mailto:ddaney@...iumnetworks.com]
> Sent: Wednesday, November 24, 2010 9:18 AM
> To: Stephen Neuendorffer
> Cc: michael@...erman.id.au; LKML; linux-mips; microblaze-uclinux@...e.uq.edu.au; devicetree-
> discuss@...ts.ozlabs.org; linuxppc-dev list; sparclinux@...r.kernel.org
> Subject: Re: Mega rename of device tree routines from of_*() to dt_*()
> 
> On 11/24/2010 09:02 AM, Stephen Neuendorffer wrote:
> >
> >
> >> -----Original Message-----
> >> From: linuxppc-dev-bounces+stephen=neuendorffer.name@...ts.ozlabs.org [mailto:linuxppc-dev-
> >> bounces+stephen=neuendorffer.name@...ts.ozlabs.org] On Behalf Of Michael Ellerman
> >> Sent: Wednesday, November 24, 2010 6:04 AM
> >> To: LKML
> >> Cc: linux-mips; microblaze-uclinux@...e.uq.edu.au; devicetree-discuss@...ts.ozlabs.org; linuxppc-
> dev
> >> list; sparclinux@...r.kernel.org
> >> Subject: RFC: Mega rename of device tree routines from of_*() to dt_*()
> >>
> >> Hi all,
> >>
> >> There were some murmurings on IRC last week about renaming the of_*()
> >> routines. I was procrastinating at the time and said I'd have a look at
> >> it, so here I am.
> >>
> >> 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".
> >>
> >> Personally I'm a bit ambivalent about it, the OF name is a bit wrong so
> >> it would be nice to get rid of, but it's a lot of churn.
> >>
> >> So I'm hoping people with either say "YES this is a great idea", or "NO
> >> this is stupid".
> >
> > Personally, I think it's a great idea, if only because I stared long and hard
> > at the code once upon a time trying to figure out what is really OF-related
> > and what isn't.  It's somewhat clearer now that drivers/of has been factored
> > out (although, shouldn't it be drivers/dt???)
> >
> > That said, it *is* alot of code churn.  If it's going to be done, I think it should be
> > done in concert with fixing a bunch of the function names which don't really follow any
> > sane naming convention, so that the backporting discontinuity only happens once.
> >
> 
> Oh, you mean things like:
> 
> of_{,un}register_platform_driver vs. platform_driver_{,un}register
> 
> That one is particularly annoying to me.
> 
> David Daney

Actually, I was particularly thinking of drivers/of/fdt.c, which I was recently hacking around with,
but I'm sure there are others... :)

Steve

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.