Thread (36 messages) 36 messages, 2 authors, 2016-08-31

[PATCH v7 14/14] Documentation: remove the constraint on the distances of node pairs

From: Will Deacon <hidden>
Date: 2016-08-26 15:35:52
Also in: linux-devicetree, lkml

On Wed, Aug 24, 2016 at 03:44:53PM +0800, Zhen Lei wrote:
quoted hunk ↗ jump to hunk
Update documentation. This limit is unneccessary.

Signed-off-by: Zhen Lei <redacted>
Acked-by: Rob Herring <robh@kernel.org>
---
 Documentation/devicetree/bindings/numa.txt | 1 -
 1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/numa.txt b/Documentation/devicetree/bindings/numa.txt
index 21b3505..c0ea4a7 100644
--- a/Documentation/devicetree/bindings/numa.txt
+++ b/Documentation/devicetree/bindings/numa.txt
@@ -48,7 +48,6 @@ distance (memory latency) between all numa nodes.

   Note:
 	1. Each entry represents distance from first node to second node.
-	The distances are equal in either direction.
Hmm, so what happens now if firmware provides a description where both
distances (in either direction) are supplied, but are different?

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help