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:	Thu, 19 Sep 2013 11:49:41 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	David Gibson <david@...son.dropbear.id.au>
CC:	Jon Loeliger <jdl@....com>, Olof Johansson <olof@...om.net>,
	frowand.list@...il.com, Tomasz Figa <tomasz.figa@...il.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Rob Herring <rob.herring@...xeda.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [dtc PATCH] Ensure all tests have matching reg and unit address

On 09/19/2013 06:18 AM, David Gibson wrote:
> On Wed, Sep 18, 2013 at 02:23:02PM -0600, Stephen Warren wrote:
>> From: Stephen Warren <swarren@...dia.com>
>> 
>> ePAPR 1.1 section 2.2.1.1 "Node Name Requirements" specifies that
>> any node that has a reg property must include a unit address in
>> its name with value matching the first entry in its reg property.
>> Conversely, if a node does not have a reg property, the node name
>> must not include a unit address.
>> 
>> Adjust all the dtc test-cases to conform to this rule.
>> 
>> Signed-off-by: Stephen Warren <swarren@...dia.com>
> 
> Yeah, the testcase examples were built as purely syntactic
> exercises without really considering dt content conventions.
> Fixing them up is arguably unnnecessary, but certainly doesn't hurt
> and makes them better as examples.
> 
> Applied and pushed.

Strange; I see that the git author field ended up as you rather than
me. Did you need to apply the patch manually for some reason (if so,
what did I do wrong?) or did something go wrong in the patch
application process?
--
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