[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220107030553.398321-1-qhjin.dev@gmail.com>
Date: Fri, 7 Jan 2022 11:05:53 +0800
From: Qinghua Jin <qhjin.dev@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Qinghua Jin <qhjin.dev@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Jonathan Corbet <corbet@....net>,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] Documentation: kunit: Fix typo
Fix a typo: actualy -> actual
Signed-off-by: Qinghua Jin <qhjin.dev@...il.com>
---
Documentation/dev-tools/kunit/usage.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst
index 63f1bb89ebf5..b9940758787c 100644
--- a/Documentation/dev-tools/kunit/usage.rst
+++ b/Documentation/dev-tools/kunit/usage.rst
@@ -615,7 +615,7 @@ kunit_tool) only fully supports running tests inside of UML and QEMU; however,
this is only due to our own time limitations as humans working on KUnit. It is
entirely possible to support other emulators and even actual hardware, but for
now QEMU and UML is what is fully supported within the KUnit Wrapper. Again, to
-be clear, this is just the Wrapper. The actualy KUnit tests and the KUnit
+be clear, this is just the Wrapper. The actual KUnit tests and the KUnit
library they are written in is fully architecture agnostic and can be used in
virtually any setup, you just won't have the benefit of typing a single command
out of the box and having everything magically work perfectly.
--
2.30.2
Powered by blists - more mailing lists