Commit ff1e81a7 authored by Sameer Rahmani's avatar Sameer Rahmani Committed by Jonathan Corbet
Browse files

Documentation: build warnings related to missing blank lines after explicit markups has been fixed 



Fix for several documentation build warnings related to missing blank lines
after explicit mark up.

Exact warning message:
 WARNING: Explicit markup ends without a blank line; unexpected unindent.

Signed-off-by: default avatarSameer Rahmani <lxsameer@gnu.org>
Link: https://lore.kernel.org/r/20200203201543.24834-1-lxsameer@gnu.org


Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 36a375c6

Documentation/doc-guide/contributing.rst

+1 −0
Original line number Diff line number Diff line 
.. SPDX-License-Identifier: GPL-2.0



How to help improve kernel documentation

========================================

Documentation/doc-guide/maintainer-profile.rst

+1 −0
Original line number Diff line number Diff line 
.. SPDX-License-Identifier: GPL-2.0



Documentation subsystem maintainer entry profile

================================================

Documentation/trace/kprobetrace.rst

+1 −1
Original line number Diff line number Diff line
@@ -97,6 +97,7 @@ which shows given pointer in "symbol+offset" style. 
For $comm, the default type is "string"; any other type is invalid.



.. _user_mem_access:



User Memory Access

------------------

Kprobe events supports user-space memory access. For that purpose, you can use
@@ -252,4 +253,3 @@ And you can see the traced information via /sys/kernel/debug/tracing/trace. 
Each line shows when the kernel hits an event, and <- SYMBOL means kernel

returns from SYMBOL(e.g. "sys_open+0x1b/0x1d <- do_sys_open" means kernel

returns from do_sys_open to sys_open+0x1b).

CRA Git | Maintained and supported by SUSTech CRA and CCSE