[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240807170029.3c1ff651@gandalf.local.home>
Date: Wed, 7 Aug 2024 17:00:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
<linux-trace-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
linux-hardening@...r.kernel.org
Cc: Kees Cook <kees@...nel.org>, Tony Luck <tony.luck@...el.com>,
"Guilherme G. Piccoli"@web.codeaurora.org,
Jonathan Corbet <corbet@....net>, Mike Rapoport <rppt@...nel.org>
Subject: [PATCH] pstore/ramoops: Fix typo as there is no "reserver"
From: Steven Rostedt <rostedt@...dmis.org>
For some reason my finger always hits the 'r' after typing "reserve".
Fix the typo in the Documentation example.
Fixes: d9d814eebb1ae ("pstore/ramoops: Add ramoops.mem_name= command line option")
Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
---
Note, I did have this fixed, but the previous version was pulled:
https://lore.kernel.org/linux-trace-kernel/20240613233446.283241953@goodmis.org/
Documentation/admin-guide/ramoops.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/ramoops.rst b/Documentation/admin-guide/ramoops.rst
index 6f534a707b2a..2eabef31220d 100644
--- a/Documentation/admin-guide/ramoops.rst
+++ b/Documentation/admin-guide/ramoops.rst
@@ -129,7 +129,7 @@ Setting the ramoops parameters can be done in several different manners:
takes a size, alignment and name as arguments. The name is used
to map the memory to a label that can be retrieved by ramoops.
- reserver_mem=2M:4096:oops ramoops.mem_name=oops
+ reserve_mem=2M:4096:oops ramoops.mem_name=oops
You can specify either RAM memory or peripheral devices' memory. However, when
specifying RAM, be sure to reserve the memory by issuing memblock_reserve()
--
2.43.0
Powered by blists - more mailing lists