From patchwork Fri Sep 30 06:35:27 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhao Gongyi X-Patchwork-Id: 12994952 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 26BEAC43219 for ; Fri, 30 Sep 2022 06:39:47 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F13796B0072; Fri, 30 Sep 2022 02:39:45 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EC1B08D0003; Fri, 30 Sep 2022 02:39:45 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D8A1B6B0074; Fri, 30 Sep 2022 02:39:45 -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 AFB258D0002 for ; Fri, 30 Sep 2022 02:39:45 -0400 (EDT) Received: from smtpin22.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 6C7F0405EB for ; Fri, 30 Sep 2022 06:39:45 +0000 (UTC) X-FDA: 79967801130.22.10DA4BA Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by imf21.hostedemail.com (Postfix) with ESMTP id A2C991C0007 for ; Fri, 30 Sep 2022 06:39:44 +0000 (UTC) Received: from canpemm500005.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4Mf0pf3JZbzlVlX; Fri, 30 Sep 2022 14:35:22 +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; Fri, 30 Sep 2022 14:39:41 +0800 From: Zhao Gongyi To: , , , CC: , , , , , Subject: [PATCH -next v5 4/4] docs: notifier-error-inject: Correct test's name Date: Fri, 30 Sep 2022 14:35:27 +0800 Message-ID: <20220930063527.108389-5-zhaogongyi@huawei.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220930063527.108389-1-zhaogongyi@huawei.com> References: <20220930063527.108389-1-zhaogongyi@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.67.174.63] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To canpemm500005.china.huawei.com (7.192.104.229) X-CFilter-Loop: Reflected ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664519985; a=rsa-sha256; cv=none; b=gtTfiJ970Mb8UknpME5tkMwhOPe+y98+O59z/UMZ2qDxHvbQjYd9CrQEZy/STtfGe4PWJu +mNGZ8iLSJKqW+9dDiXR5w8IG/DShYMUNFK4hnqbUxMK+OYJwoUI84WprEY/aLLYjHznnv X2gbeO6o8SNwD22W4w96UO1X9TATBTw= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.187 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=1664519985; 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=UBGvH8KDN9xLDtuXOHrMauwIjCuf8/zFXgcCG22a6qBu+fe0J3HVnKzfNDAb2ckLVO9NSj Tq3mKTAWuvu4RXfvYdIrxaQuZeaEuChhImBU21Rulb//pEzHcLX0P8RxNpES2ITxInoUUd Lf45MqQGDd1XJf/EELi+ELsjrn6DwWU= X-Stat-Signature: ey9z1ttqqhegnewni8h3e8ush8fyf7z9 X-Rspamd-Queue-Id: A2C991C0007 X-Rspam-User: Authentication-Results: imf21.hostedemail.com; dkim=none; spf=pass (imf21.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com X-Rspamd-Server: rspam01 X-HE-Tag: 1664519984-512173 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.