Remove the extra 'we '.
Signed-off-by: Shiyang Ruan <[email protected]>
---
Documentation/nvdimm/nvdimm.txt | 4 ++--
1 file 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
ACPI based systems is that there is only ever one platform-global NFIT.
That said, it is trivial to register multiple NFITs, the specification
does not preclude it. The infrastructure supports multiple busses and
-we we use this capability to test multiple NFIT configurations in the
-unit test.
+we use this capability to test multiple NFIT configurations in the unit
+test.
LIBNVDIMM: control class device in /sys/class
--
2.17.0
On Thu, 9 May 2019 15:40:49 +0800
Shiyang Ruan <[email protected]> wrote:
> Remove the extra 'we '.
>
> Signed-off-by: Shiyang Ruan <[email protected]>
> ---
> Documentation/nvdimm/nvdimm.txt | 4 ++--
> 1 file 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
> ACPI based systems is that there is only ever one platform-global NFIT.
> That said, it is trivial to register multiple NFITs, the specification
> does not preclude it. The infrastructure supports multiple busses and
> -we we use this capability to test multiple NFIT configurations in the
> -unit test.
> +we use this capability to test multiple NFIT configurations in the unit
> +test.
Applied, thanks.
I note this has languished for a bit; please don't hesitate to ping after
a week or so if you don't get a response on a patch posting.
jon