linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] doc: fix manpage formatting
Date: Sun, 21 Jan 2018 05:46:44 +0100	[thread overview]
Message-ID: <20180121044644.90500-1-luc.vanoostenryck@gmail.com> (raw)

A '.TP' was missing when describing '-fmem-report'.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 sparse.1 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sparse.1 b/sparse.1
index fbe1784da..88343f317 100644
--- a/sparse.1
+++ b/sparse.1
@@ -371,6 +371,7 @@ The \fIdir\fR name would normally take the form of the target's
 normalized GNU triplet. (e.g. i386-linux-gnu).
 .
 .SH DEBUG OPTIONS
+.TP
 .B \-fmem-report
 Report some statistics about memory allocation used by the tool.
 .
-- 
2.16.0


             reply	other threads:[~2018-01-21  4:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21  4:46 Luc Van Oostenryck [this message]
2018-01-23 11:03 ` [PATCH] doc: fix manpage formatting Christopher Li
2018-01-24  8:18   ` Luc Van Oostenryck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180121044644.90500-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).