linux-kernel - Re: [PATCH 3/3] [POWERPC] dts: kill hardcoded phandles

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] [day] [month] [year] [list]

Date:	Wed, 9 May 2007 09:30:26 +1000
From:	David Gibson <david@...son.dropbear.id.au>
To:	Loeliger Jon-LOELIGER <jdl@...escale.com>
Cc:	Vitaly Bordug <vitb@...nel.crashing.org>, linuxppc-dev@...abs.org,
	linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] [POWERPC] dts: kill hardcoded phandles

On Tue, May 08, 2007 at 07:29:20AM -0700, Jon Loeliger wrote:
> 
> > > -       interrupt-controller@...00000 {
> > > -               linux,phandle = <f8200000>;
> > > +		pci_pic:interrupt-controller@...00000 {
> > 
> > I'd like to establish a convention of putting a space after the : and
> > using capitals for labels unless there's a strong reason not to in a
> > particular case.  It makes them easier to visually distinguish next to
> > the node name.
> 
> Colon-space is easy and I'll buy it.
> I'm not big on uppercase shouting, though.

I don't think it will really be any more shouty than the convention of
using caps for simple constant #defines.  The Ebony device tree uses
this now, and I think it turns out quite well (though in that case
there's the additional reason to use caps that the labels are based on
the component names used in the 440GP user manual, which are given as
caps).

-- 
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/