From: Kemeng Shi <shikemeng@huaweicloud.com>
To: brendan.higgins@linux.dev, davidgow@google.com, rmoar@google.com,
corbet@lwn.net
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: kunit: correct KUNIT_VERY_SLOW to KUNIT_SPEED_VERY_SLOW
Date: Thu, 21 Mar 2024 01:14:24 +0800 [thread overview]
Message-ID: <20240320171424.6536-1-shikemeng@huaweicloud.com> (raw)
There is no KUNIT_VERY_SLOW, I guess we mean KUNIT_SPEED_VERY_SLOW.
Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
---
Documentation/dev-tools/kunit/running_tips.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/dev-tools/kunit/running_tips.rst b/Documentation/dev-tools/kunit/running_tips.rst
index bd689db6fdd2..482f598d141c 100644
--- a/Documentation/dev-tools/kunit/running_tips.rst
+++ b/Documentation/dev-tools/kunit/running_tips.rst
@@ -294,7 +294,7 @@ macro to define the test case instead of ``KUNIT_CASE(test_name)``.
.. code-block:: c
static const struct kunit_attributes example_attr = {
- .speed = KUNIT_VERY_SLOW,
+ .speed = KUNIT_SPEED_VERY_SLOW,
};
static struct kunit_case example_test_cases[] = {
@@ -311,7 +311,7 @@ suite definition.
.. code-block:: c
static const struct kunit_attributes example_attr = {
- .speed = KUNIT_VERY_SLOW,
+ .speed = KUNIT_SPEED_VERY_SLOW,
};
static struct kunit_suite example_test_suite = {
--
2.30.0
next reply other threads:[~2024-03-20 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 17:14 Kemeng Shi [this message]
2024-03-22 4:12 ` David Gow
2024-04-02 16:15 ` Jonathan Corbet
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=20240320171424.6536-1-shikemeng@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
/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®