From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: util-linux@vger.kernel.org
Subject: [PATCH] doc: schedutils/*: Fix some warnings from "mandoc -T lint"
Date: Thu, 11 Jun 2020 00:18:44 +0000 [thread overview]
Message-ID: <20200611001844.GA25404@rhi.hi.is> (raw)
mandoc: ./schedutils/chrt.1:37:2: WARNING: skipping paragraph macro: PP after SH
mandoc: ./schedutils/ionice.1:120:2: WARNING: skipping paragraph macro: PP empty
mandoc: ./schedutils/taskset.1:36:2: WARNING: skipping paragraph macro: PP after SH
####
There is no change in the ouput from "nroff" and "groff".
Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
schedutils/chrt.1 | 1 -
schedutils/ionice.1 | 1 -
schedutils/taskset.1 | 1 -
3 files changed, 3 deletions(-)
diff --git a/schedutils/chrt.1 b/schedutils/chrt.1
index 83e57070c..0d9a225c3 100644
--- a/schedutils/chrt.1
+++ b/schedutils/chrt.1
@@ -34,7 +34,6 @@ chrt \- manipulate the real-time attributes of a process
.B \-p
.RI [ priority ]\ pid
.SH DESCRIPTION
-.PP
.B chrt
sets or retrieves the real-time scheduling attributes of an existing \fIpid\fR,
or runs \fIcommand\fR with the given attributes.
diff --git a/schedutils/ionice.1 b/schedutils/ionice.1
index 72dbae6af..bbb6b7e95 100644
--- a/schedutils/ionice.1
+++ b/schedutils/ionice.1
@@ -117,7 +117,6 @@ Display version information and exit.
Linux supports I/O scheduling priorities and classes since 2.6.13 with the CFQ
I/O scheduler.
.SH EXAMPLES
-.LP
.TP 7
# \fBionice\fP \-c 3 \-p 89
.TP 7
diff --git a/schedutils/taskset.1 b/schedutils/taskset.1
index 7fdc50898..71e7874e1 100644
--- a/schedutils/taskset.1
+++ b/schedutils/taskset.1
@@ -33,7 +33,6 @@ taskset \- set or retrieve a process's CPU affinity
.B \-p
.RI [ mask ]\ pid
.SH DESCRIPTION
-.PP
.B taskset
is used to set or retrieve the CPU affinity of a running process given its
\fIpid\fR, or to launch a new \fIcommand\fR with a given CPU affinity.
--
2.26.2
reply other threads:[~2020-06-11 0:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200611001844.GA25404@rhi.hi.is \
--to=bjarniig@rhi.hi.is \
--cc=util-linux@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).