Commit ddbd60c779b4 ("kunit: use --build_dir=.kunit as default") changed the default --build_dir, which had the side effect of making `.kunitconfig` move to `.kunit/.kunitconfig`.

However, the first few lines of kunit/start.rst never got updated, oops.

Fix this by telling people to run kunit.py first, which will automatically generate the .kunit directory and .kunitconfig file, and then edit the file manually as desired.

Reported-by: Yifan Yuan alpc_metic@live.com Signed-off-by: Daniel Latypov dlatypov@google.com --- Documentation/dev-tools/kunit/start.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/dev-tools/kunit/start.rst b/Documentation/dev-tools/kunit/start.rst index 1e00f9226f74..65f4ef6c1f4c 100644 --- a/Documentation/dev-tools/kunit/start.rst +++ b/Documentation/dev-tools/kunit/start.rst @@ -31,14 +31,15 @@ This file essentially contains the regular Kernel config, with the specific test targets as well. The ``.kunitconfig`` should also contain any other config options required by the tests.

-A good starting point for a ``.kunitconfig`` is the KUnit defconfig: +If you run KUnit, it'll generate one automatically for you.

.. code-block:: bash

cd $PATH_TO_LINUX_REPO - cp tools/testing/kunit/configs/default.config .kunitconfig + ./tools/testing/kunit/kunit.py run + cat .kunit/.kunitconfig

-You can then add any other Kconfig options you wish, e.g.: +You can then edit that file to add any other Kconfig options you wish, e.g.:

.. code-block:: none

base-commit: 52a5d80a2225e2d0b2a8f4656b76aead2a443b2a