[<prev] [next>] [day] [month] [year] [list]
Message-ID: <41bc35342567227eb73c1b7683870b5975b9241c.1726643608.git.joerg@jo-so.de>
Date: Wed, 18 Sep 2024 09:13:28 +0200
From: Jörg Sommer <joerg@...so.de>
To: linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Kees Cook <keescook@...omium.org>,
Jörg Sommer <joerg@...so.de>
Subject: [PATCH] doc/pstore: Fix parameter names in examples
Signed-off-by: Jörg Sommer <joerg@...so.de>
---
Documentation/admin-guide/pstore-blk.rst | 2 +-
Documentation/admin-guide/ramoops.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/pstore-blk.rst b/Documentation/admin-guide/pstore-blk.rst
index 1bb2a1c292aa..5c247c25e13a 100644
--- a/Documentation/admin-guide/pstore-blk.rst
+++ b/Documentation/admin-guide/pstore-blk.rst
@@ -35,7 +35,7 @@ module parameters have priority over Kconfig.
Here is an example for module parameters::
- pstore_blk.blkdev=/dev/mmcblk0p7 pstore_blk.kmsg_size=64 best_effort=y
+ pstore_blk.blkdev=/dev/mmcblk0p7 pstore_blk.kmsg_size=64 pstore_blk.best_effort=y
The detail of each configurations may be of interest to you.
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.45.2
Powered by blists - more mailing lists