summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShiyang Ruan <ruansy.fnst@cn.fujitsu.com>2019-05-09 03:40:49 -0400
committerJonathan Corbet <corbet@lwn.net>2019-06-07 13:39:04 -0400
commit3d9cf48b2ca257f1a249b347236098c3cf9d54f1 (patch)
tree059b1b17ca2e7d7b3b441a1fc70e34d42521ec91
parentbed0918d64ca28169d55bd138ed20f09e288303e (diff)
Documentation: nvdimm: Fix typo
Remove the extra 'we '. Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/nvdimm/nvdimm.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/nvdimm/nvdimm.txt b/Documentation/nvdimm/nvdimm.txt
index e894de69915a..1669f626b037 100644
--- a/Documentation/nvdimm/nvdimm.txt
+++ b/Documentation/nvdimm/nvdimm.txt
@@ -284,8 +284,8 @@ A bus has a 1:1 relationship with an NFIT. The current expectation for
284ACPI based systems is that there is only ever one platform-global NFIT. 284ACPI based systems is that there is only ever one platform-global NFIT.
285That said, it is trivial to register multiple NFITs, the specification 285That said, it is trivial to register multiple NFITs, the specification
286does not preclude it. The infrastructure supports multiple busses and 286does not preclude it. The infrastructure supports multiple busses and
287we we use this capability to test multiple NFIT configurations in the 287we use this capability to test multiple NFIT configurations in the unit
288unit test. 288test.
289 289
290LIBNVDIMM: control class device in /sys/class 290LIBNVDIMM: control class device in /sys/class
291 291