From: sj38.park@gmail.com
To: shuah@kernel.org
Cc: brendanhiggins@google.com, corbet@lwn.net,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
sj38.park@gmail.com, sjpark@amazon.com, sjpark@amazon.de
Subject: [PATCH v7 1/6] docs/kunit/start: Use in-tree 'kunit_defconfig'
Date: Fri, 20 Dec 2019 05:14:03 +0000 [thread overview]
Message-ID: <20191220051408.3591-2-sjpark@amazon.de> (raw)
In-Reply-To: <20191220051408.3591-1-sjpark@amazon.de>
From: SeongJae Park <sjpark@amazon.de>
The kunit doc suggests users to get the default `kunitconfig` from an
external git tree. However, the file is already located under the
`arch/um/configs/` of the kernel tree. Because the local file is easier
to access and maintain, this commit updates the doc to use it.
Signed-off-by: SeongJae Park <sjpark@amazon.de>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Tested-by: Brendan Higgins <brendanhiggins@google.com>
---
Documentation/dev-tools/kunit/start.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/dev-tools/kunit/start.rst b/Documentation/dev-tools/kunit/start.rst
index 9d6db892c41c..d5197f1a45cb 100644
--- a/Documentation/dev-tools/kunit/start.rst
+++ b/Documentation/dev-tools/kunit/start.rst
@@ -32,9 +32,8 @@ regular Kernel config, with the specific test targets as well.
.. code-block:: bash
- git clone -b master https://kunit.googlesource.com/kunitconfig $PATH_TO_KUNITCONFIG_REPO
cd $PATH_TO_LINUX_REPO
- ln -s $PATH_TO_KUNIT_CONFIG_REPO/kunitconfig kunitconfig
+ cp arch/um/configs/kunit_defconfig kunitconfig
You may want to add kunitconfig to your local gitignore.
--
2.17.1
next prev parent reply other threads:[~2019-12-20 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 5:14 [PATCH v7 0/6] Fix nits in the kunit sj38.park
2019-12-20 5:14 ` sj38.park [this message]
2019-12-20 5:14 ` [PATCH v7 2/6] kunit: Remove duplicated defconfig creation sj38.park
2019-12-20 5:14 ` [PATCH v7 3/6] kunit: Create default config in '--build_dir' sj38.park
2019-12-20 5:14 ` [PATCH v7 4/6] kunit: Place 'test.log' under the 'build_dir' sj38.park
2019-12-20 5:14 ` [PATCH v7 5/6] kunit: Rename 'kunitconfig' to '.kunitconfig' sj38.park
2019-12-20 5:14 ` [PATCH v7 6/6] kunit/kunit_tool_test: Test '--build_dir' option run sj38.park
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=20191220051408.3591-2-sjpark@amazon.de \
--to=sj38.park@gmail.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
/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;
as well as URLs for NNTP newsgroup(s).