On Wed, Aug 07, 2024 at 05:00:29PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@xxxxxxxxxxx>
>
> 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@xxxxxxxxxxx>
Acked-by: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>
> ---
> Note, I did have this fixed, but the previous version was pulled:
> https://lore.kernel.org/linux-trace-kernel/20240613233446.283241953@xxxxxxxxxxx/
>
> 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
>
--
Sincerely yours,
Mike.
