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]
Date:	Mon, 22 Jul 2013 15:53:53 +0200
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Lee Jones" <lee.jones@...aro.org>
cc:	"Christian Daudt" <csd@...adcom.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, linus.walleij@...ricsson.com
Subject: Re: [PATCH 05/22] ARM: dts: bcm281xx: Remove '0x's from
 BCM11351 BRT DTS file

On 07/22/2013 03:38 PM, Lee Jones wrote:
> On Mon, 22 Jul 2013, Christian Daudt wrote:
>
>> On 13-07-22 03:52 AM, Lee Jones wrote:
>>> Cc: Christian Daudt <csd@...adcom.com>
>>> Signed-off-by: Lee Jones <lee.jones@...aro.org>
>>> ---
>>>   arch/arm/boot/dts/bcm11351-brt.dts | 6 +++---
>>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/bcm11351-brt.dts b/arch/arm/boot/dts/bcm11351-brt.dts
>>> index 67ec524..fdace5d 100644
>>> --- a/arch/arm/boot/dts/bcm11351-brt.dts
>>> +++ b/arch/arm/boot/dts/bcm11351-brt.dts
>>> @@ -27,18 +27,18 @@
>>>   		status = "okay";
>>>   	};
>>> -	sdio0: sdio@...f180000 {
>>> +	sdio0: sdio@...80000 {
>>>   		max-frequency = <48000000>;
>>>   		status = "okay";
>>>   	};
>>> -	sdio1: sdio@...f190000 {
>>> +	sdio1: sdio@...90000 {
>>>   		non-removable;
>>>   		max-frequency = <48000000>;
>>>   		status = "okay";
>>>   	};
>>> -	sdio3: sdio@...f1b0000 {
>>> +	sdio3: sdio@...b0000 {
>>>   		max-frequency = <48000000>;
>>>   		status = "okay";
>>>   	};
>> Hi Lee,
>>   Is this convention documented ? Someone called my attention to the
>> fact that this dts files was inconsistent in its use of 0x in names,
>> but I was not aware of a coding guideline for this.
>
> The best two places I can think of are:
>
> Documentation/devicetree/usage-model.txt
> and
> http://www.devicetree.org/Device_Tree_Usage

And even those do not stick to a single convention, but that is what can 
be expected of a twiki page :-p

Regards,
Arend


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ