From patchwork Fri Sep 9 07:52:00 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhao Gongyi X-Patchwork-Id: 12971198 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 DE84DECAAA1 for ; Fri, 9 Sep 2022 07:55:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id DA85E94000A; Fri, 9 Sep 2022 03:55:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B54EC940007; Fri, 9 Sep 2022 03:55:42 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9A498940009; Fri, 9 Sep 2022 03:55:42 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 8BEB9940007 for ; Fri, 9 Sep 2022 03:55:42 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 7059E8024D for ; Fri, 9 Sep 2022 07:55:42 +0000 (UTC) X-FDA: 79891787724.01.86ABCE1 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by imf12.hostedemail.com (Postfix) with ESMTP id E192540094 for ; Fri, 9 Sep 2022 07:55:41 +0000 (UTC) Received: from canpemm500005.china.huawei.com (unknown [172.30.72.55]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4MP7Vn5hs4zmVM4; Fri, 9 Sep 2022 15:52:01 +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.24; Fri, 9 Sep 2022 15:55:39 +0800 From: Zhao Gongyi To: , , , CC: , , , , , Zhao Gongyi Subject: [PATCH -next 5/5] docs: notifier-error-inject: Correct test's name Date: Fri, 9 Sep 2022 15:52:00 +0800 Message-ID: <20220909075200.198363-6-zhaogongyi@huawei.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220909075200.198363-1-zhaogongyi@huawei.com> References: <20220909075200.198363-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=1662710142; a=rsa-sha256; cv=none; b=5TY/YGWeO5TOghQLiDnFltsOOJhPZBWN/Ul5wYALzQgX3Wu7Inu2PkAxhWUmgiFlogUNsa YjSfUH5ms1KOXly/XK0NaD0BI1jS/GVuWMhiDx1hAI/RewRse4PfUG2YSI0LbaEDeLpLsW NCHfUMGluDaX1kNgbkAtjAn9PgO9uhQ= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf12.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=1662710142; 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=h39W/NM0cD//sI4lV6iyHr4bmmoOMEEvd87rAebCJfU=; b=mRdtBkleqqj/dJGUYzr9uFGZi06kdspsJD+lORVyGm/9ikkkOzV+amThjJPXy32KtzjiAJ dISptm3RJbFN3w+98IaaHFl2TTanQDiLjeA7fc0K/CaHYT9Z7PTvgGl3wtDS4k4nsAxYgl i79gHi6ltgXjFmip0r6HbkqBhCo+sJs= Authentication-Results: imf12.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf12.hostedemail.com: domain of zhaogongyi@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=zhaogongyi@huawei.com X-Rspam-User: X-Rspamd-Queue-Id: E192540094 X-Rspamd-Server: rspam09 X-Stat-Signature: 4i8f8ubnxtn87bjw86xztta8guibi4kq X-HE-Tag: 1662710141-696041 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 0e2790122166..170c583eb5bc 100644 --- a/Documentation/fault-injection/notifier-error-inject.rst +++ b/Documentation/fault-injection/notifier-error-inject.rst @@ -95,8 +95,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.