From patchwork Mon Sep 26 13:03:41 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhao Gongyi X-Patchwork-Id: 12988686 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 47BE3C6FA83 for ; Mon, 26 Sep 2022 13:07:41 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 07E178E0039; Mon, 26 Sep 2022 09:07:39 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 02D918E0047; Mon, 26 Sep 2022 09:07:38 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E5DC78E0039; Mon, 26 Sep 2022 09:07:38 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id D630B8E0047 for ; Mon, 26 Sep 2022 09:07:38 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id B1D19120C88 for ; Mon, 26 Sep 2022 13:07:38 +0000 (UTC) X-FDA: 79954263396.30.A7D570E Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by imf22.hostedemail.com (Postfix) with ESMTP id 0510EC0026 for ; Mon, 26 Sep 2022 13:07:37 +0000 (UTC) Received: from canpemm500005.china.huawei.com (unknown [172.30.72.53]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4MbjcM58xgzWh5P; Mon, 26 Sep 2022 21:03:31 +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; Mon, 26 Sep 2022 21:07:34 +0800 From: Zhao Gongyi To: , , , CC: , , , , , Zhao Gongyi Subject: [PATCH -next v3 3/3] docs: notifier-error-inject: Correct test's name Date: Mon, 26 Sep 2022 21:03:41 +0800 Message-ID: <20220926130341.253039-4-zhaogongyi@huawei.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220926130341.253039-1-zhaogongyi@huawei.com> References: <20220926130341.253039-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=1664197658; a=rsa-sha256; cv=none; b=enSAP5G4Pgk88lpBbiaqC+dAofYmc0O48kj8zlAKrZr17Hr261We8rSxt9IjweeeB0tLMe dZB42/V6tqHyfPEU8g/blNPBude9DFJl6vNY0n2/5DXD3sd7MjAcm9dYYT9vhetTLb+vcb uzQFUjyGmpjmS7Td2M87NqE8U2b3s7c= ARC-Authentication-Results: i=1; imf22.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf22.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664197658; 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=MvtxUswiCti/QnmFwW5yyayTOyJW+UUO2Tf0Kj2J0LR351H9td9CgdRYgAdk0AGMckpK1v Kkzg+dg11P1I+z6Bj7f1oWOL4jaf3lJDn5r26hHYpwMDf5NUL/re1pUVGxE4e3IvF2nZnf gE2IH0YcOI+VqjT3QhmnxXvTmPC9W80= X-Rspamd-Server: rspam03 X-Rspam-User: Authentication-Results: imf22.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf22.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com X-Stat-Signature: bzcozn3uoes3pmkqaez6gomtij3m6553 X-Rspamd-Queue-Id: 0510EC0026 X-HE-Tag: 1664197657-921122 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.