mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah@kernel.org
Subject: [GIT PULL] KUnit update for Linux 5.18-rc2
Date: Fri, 8 Apr 2022 12:55:58 -0600	[thread overview]
Message-ID: <f8e5687f-958b-c97b-4ddb-7bbfbdfa036f@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]

Hi Linus,

Please pull the following KUnit fixes update for Linux 5.18-rc2.

This KUnit update for Linux 5.18-rc2 consists of a single documentation
fix to incorrect and outdated usage information.

diff is attached.

thanks,
-- Shuah

----------------------------------------------------------------
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

   Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux-kselftest-kunit-fixes-5.18-rc2

for you to fetch changes up to 02c7efa43627163e489a8db87882445a0ff381f7:

   Documentation: kunit: fix path to .kunitconfig in start.rst (2022-04-04 12:02:44 -0600)

----------------------------------------------------------------
linux-kselftest-kunit-fixes-5.18-rc2

This KUnit update for Linux 5.18-rc2 consists of a single documentation
fix to incorrect and outdated usage information.

----------------------------------------------------------------
Daniel Latypov (1):
       Documentation: kunit: fix path to .kunitconfig in start.rst

  Documentation/dev-tools/kunit/start.rst | 11 ++++++++---
  1 file changed, 8 insertions(+), 3 deletions(-)
----------------------------------------------------------------

[-- Attachment #2: linux-kselftest-kunit-fixes-5.18-rc2.diff --]
[-- Type: text/x-patch, Size: 969 bytes --]

diff --git a/Documentation/dev-tools/kunit/start.rst b/Documentation/dev-tools/kunit/start.rst
index ad168d16968f..867a4bba6bf6 100644
--- a/Documentation/dev-tools/kunit/start.rst
+++ b/Documentation/dev-tools/kunit/start.rst
@@ -41,13 +41,18 @@ or ``VFAT_FS``. To run ``FAT_KUNIT_TEST``, the ``.kunitconfig`` has:
 	CONFIG_MSDOS_FS=y
 	CONFIG_FAT_KUNIT_TEST=y
 
-1. A good starting point for the ``.kunitconfig``, is the KUnit default
-   config. Run the command:
+1. A good starting point for the ``.kunitconfig`` is the KUnit default config.
+   You can generate it by running:
 
 .. code-block:: bash
 
 	cd $PATH_TO_LINUX_REPO
-	cp tools/testing/kunit/configs/default.config .kunitconfig
+	tools/testing/kunit/kunit.py config
+	cat .kunit/.kunitconfig
+
+.. note ::
+   ``.kunitconfig`` lives in the ``--build_dir`` used by kunit.py, which is
+   ``.kunit`` by default.
 
 .. note ::
    You may want to remove CONFIG_KUNIT_ALL_TESTS from the ``.kunitconfig`` as

             reply	other threads:[~2022-04-08 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 18:55 Shuah Khan [this message]
2022-04-09  1:09 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f8e5687f-958b-c97b-4ddb-7bbfbdfa036f@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®