From patchwork Tue Sep 27 03:28:51 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhao Gongyi X-Patchwork-Id: 12989836 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 24E0EC6FA82 for ; Tue, 27 Sep 2022 03:32:56 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E47328E00A8; Mon, 26 Sep 2022 23:32:54 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id DA8FA8E0090; Mon, 26 Sep 2022 23:32:54 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B83378E00A8; Mon, 26 Sep 2022 23:32:54 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id A5D0A8E0090 for ; Mon, 26 Sep 2022 23:32:54 -0400 (EDT) Received: from smtpin14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 5A44A160324 for ; Tue, 27 Sep 2022 03:32:54 +0000 (UTC) X-FDA: 79956443868.14.F5A2DA8 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by imf21.hostedemail.com (Postfix) with ESMTP id 2CE861C0009 for ; Tue, 27 Sep 2022 03:32:52 +0000 (UTC) Received: from canpemm500005.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4Mc4pg4SNQzWgsB; Tue, 27 Sep 2022 11:28:43 +0800 (CST) Received: from ubuntu1804.huawei.com (10.67.174.63) by canpemm500005.china.huawei.com (7.192.104.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 27 Sep 2022 11:32:47 +0800 From: Zhao Gongyi To: , , , CC: , , , , , Subject: [PATCH -next v4 3/3] docs: notifier-error-inject: Correct test's name Date: Tue, 27 Sep 2022 11:28:51 +0800 Message-ID: <20220927032851.128174-4-zhaogongyi@huawei.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220927032851.128174-1-zhaogongyi@huawei.com> References: <20220927032851.128174-1-zhaogongyi@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.67.174.63] X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To canpemm500005.china.huawei.com (7.192.104.229) X-CFilter-Loop: Reflected ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664249572; a=rsa-sha256; cv=none; b=NwxwOHIbwOGlOXI+RmqCIW54PWh9FpfgcJuFFbGZVB0RTIoLFcoaH5ZNSUPHb9qZ5NlJOJ vDwrCvkYZvUkyecd+fw+0oFYNDYYDcQUTUDHNy6wfcklGeeFwXFBrXnqmAd+HnD3WtJc6R LeYhHKxwqBsYapda/QjlWwGqQWarXt0= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664249572; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=r1ZDDIW2eFS2NJbuhgxKbpf1IivBqY4os6rjBiejqgk=; b=TkD/5ut2SGvu48p3oRm2tzbLwEbGDslb2w9P6Ez0kGlHzh4CxjlgxMxKcNMOzIl/Zh40UB EJrgxxQygEBAw6mK6KMxtiB727b/S6Gn5pTwTVjjgkwRxUdyWzNPX+4CkRpTRcoX6mZ7dA N+qemLErqavzZzXyqD1ExsV3EDpqqe0= Authentication-Results: imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com X-Stat-Signature: 8rfbt5m3teyma9u9h5udwehitapkh38z X-Rspamd-Queue-Id: 2CE861C0009 X-Rspam-User: X-Rspamd-Server: rspam05 X-HE-Tag: 1664249572-832568 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Correct test's name for mem-on-off-test.sh/cpu-on-off-test.sh. Signed-off-by: Zhao Gongyi Reviewed-by: David Hildenbrand --- Documentation/fault-injection/notifier-error-inject.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- 2.17.1 diff --git a/Documentation/fault-injection/notifier-error-inject.rst b/Documentation/fault-injection/notifier-error-inject.rst index 1668b6e48d3a..fdf2dc433ead 100644 --- a/Documentation/fault-injection/notifier-error-inject.rst +++ b/Documentation/fault-injection/notifier-error-inject.rst @@ -91,8 +91,8 @@ For more usage examples There are tools/testing/selftests using the notifier error injection features for CPU and memory notifiers. - * tools/testing/selftests/cpu-hotplug/on-off-test.sh - * tools/testing/selftests/memory-hotplug/on-off-test.sh + * tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh + * tools/testing/selftests/memory-hotplug/mem-on-off-test.sh These scripts first do simple online and offline tests and then do fault injection tests if notifier error injection module is available.