On Wed, Aug 24, 2016 at 03:44:53PM +0800, Zhen Lei wrote: > Update documentation. This limit is unneccessary. > > Signed-off-by: Zhen Lei <thunder.leizhen@xxxxxxxxxx> > Acked-by: Rob Herring <robh@xxxxxxxxxx> > --- > 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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
