[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210107125610.1576368-1-unixbhaskar@gmail.com>
Date: Thu, 7 Jan 2021 18:26:10 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: mhiramat@...nel.org, corbet@....net, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH] docs: admin-guide: bootconfig: Fix feils to fails
s/feils/fails/p
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
Documentation/admin-guide/bootconfig.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
index 9b90efcc3a35..452b7dcd7f6b 100644
--- a/Documentation/admin-guide/bootconfig.rst
+++ b/Documentation/admin-guide/bootconfig.rst
@@ -154,7 +154,7 @@ get the boot configuration data.
Because of this "piggyback" method, there is no need to change or
update the boot loader and the kernel image itself as long as the boot
loader passes the correct initrd file size. If by any chance, the boot
-loader passes a longer size, the kernel feils to find the bootconfig data.
+loader passes a longer size, the kernel fails to find the bootconfig data.
To do this operation, Linux kernel provides "bootconfig" command under
tools/bootconfig, which allows admin to apply or delete the config file
--
2.30.0
Powered by blists - more mailing lists