[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <de2e08c8b6bdf278ddd678e9ffcc820115e153b0.1616992679.git.unixbhaskar@gmail.com>
Date: Mon, 29 Mar 2021 10:42:42 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: corbet@....net, linux-doc@...r.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@...il.com>, rdunlap@...radead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 06/23] vm: hwpoison.rst: A typo fix
s/expection/exception/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
Documentation/vm/hwpoison.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/vm/hwpoison.rst b/Documentation/vm/hwpoison.rst
index a5c884293dac..727f080073dd 100644
--- a/Documentation/vm/hwpoison.rst
+++ b/Documentation/vm/hwpoison.rst
@@ -50,7 +50,7 @@ of applications. KVM support requires a recent qemu-kvm release.
For the KVM use there was need for a new signal type so that
KVM can inject the machine check into the guest with the proper
address. This in theory allows other applications to handle
-memory failures too. The expection is that near all applications
+memory failures too. The exception is that near all applications
won't do that, but some very specialized ones might.
Failure recovery modes
--
2.26.3
Powered by blists - more mailing lists