| Message ID | 20201027184853.20830-1-rdunlap@infradead.org |
|---|---|
| State | Accepted |
| Commit | f7766424cf15fd6e03e8230fb17d5612c5b76dbe |
| Headers | show |
| Series | KUnit: Docs: fix a wording typo | expand |
On Wed, Oct 28, 2020 at 2:49 AM Randy Dunlap <rdunlap@infradead.org> wrote: > > Fix a wording typo (keyboard glitch). > > Signed-off-by: Randy Dunlap <rdunlap@infradead.org> > Cc: David Gow <davidgow@google.com> > Cc: linux-kselftest@vger.kernel.org > Cc: kunit-dev@googlegroups.com > Cc: Shuah Khan <shuah@kernel.org> > Cc: Shuah Khan <skhan@linuxfoundation.org> > Cc: Brendan Higgins <brendanhiggins@google.com> > --- Whoops! Thanks for catching this! Reviewed-by: David Gow <davidgow@google.com> Cheers, -- David
--- linux-next-20201027.orig/Documentation/dev-tools/kunit/faq.rst +++ linux-next-20201027/Documentation/dev-tools/kunit/faq.rst @@ -90,7 +90,7 @@ things to try. re-run kunit_tool. 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This may help clean up any residual config items which could be causing problems. -6. Finally, try running KUnit outside UML. KUnit and KUnit tests can run be +6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be built into any kernel, or can be built as a module and loaded at runtime. Doing so should allow you to determine if UML is causing the issue you're seeing. When tests are built-in, they will execute when the kernel boots, and
Fix a wording typo (keyboard glitch). Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: David Gow <davidgow@google.com> Cc: linux-kselftest@vger.kernel.org Cc: kunit-dev@googlegroups.com Cc: Shuah Khan <shuah@kernel.org> Cc: Shuah Khan <skhan@linuxfoundation.org> Cc: Brendan Higgins <brendanhiggins@google.com> --- Documentation/dev-tools/kunit/faq.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)