summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYegor Yefremov <yegorslists@googlemail.com>2016-03-01 10:54:24 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2016-03-02 19:16:52 +0100
commit1a0cebc5722675b72080958a90f163767876da92 (patch)
tree05a740dedd20031c3ceb80f64a85d8d220eb6a00
parent74d09efa549c0287a8741018f046774f37d997cd (diff)
downloadbarebox-1a0cebc5722675b72080958a90f163767876da92.tar.gz
Documentation/filesystems: pstore: fix formatting
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--Documentation/filesystems/pstore.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/filesystems/pstore.rst b/Documentation/filesystems/pstore.rst
index 74acd87..0f3a223 100644
--- a/Documentation/filesystems/pstore.rst
+++ b/Documentation/filesystems/pstore.rst
@@ -12,6 +12,7 @@ messages are stored by the kernel in a specified RAM area which is never
overwritten by any user. This data can be accessed after a reboot through
/pstore in Barebox or the kernel. The pstore filesystem is automatically mounted
at boot::
+
none on / type ramfs
none on /dev type devfs
none on /pstore type pstore
@@ -40,7 +41,7 @@ and RAM backend support. The kernel receives the parameters describing the
layout over the kernel command line. These parameters are automatically
generated by Barebox. You can change these parameters in Barebox menuconfig. The
RAMOOPS parameters for the Kernel are stored in the variable
-global.linux.bootargs.ramoops::
+global.linux.bootargs.ramoops.
To see where the RAMOOPS area is located, you can execute iomem in Barebox. The
RAMOOPS area is listed as 'persistent ram'::