From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EF968C433E0 for ; Sat, 20 Jun 2020 23:36:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D3EAB2474C for ; Sat, 20 Jun 2020 23:36:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728405AbgFTXgy (ORCPT ); Sat, 20 Jun 2020 19:36:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37438 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728199AbgFTXgy (ORCPT ); Sat, 20 Jun 2020 19:36:54 -0400 Received: from inpost.hi.is (inpost.hi.is [IPv6:2a00:c88:4000:1650::165:62]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A32C4C061794 for ; Sat, 20 Jun 2020 16:36:53 -0700 (PDT) Received: from hekla.rhi.hi.is (hekla.rhi.hi.is [IPv6:2a00:c88:4000:1650::165:2]) by inpost.hi.is (8.14.7/8.14.7) with ESMTP id 05KNalH7029859 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 20 Jun 2020 23:36:47 GMT DKIM-Filter: OpenDKIM Filter v2.11.0 inpost.hi.is 05KNalH7029859 Received: from hekla.rhi.hi.is (localhost [127.0.0.1]) by hekla.rhi.hi.is (8.14.4/8.14.4) with ESMTP id 05KNalja008933; Sat, 20 Jun 2020 23:36:47 GMT Received: (from bjarniig@localhost) by hekla.rhi.hi.is (8.14.4/8.14.4/Submit) id 05KNalPi008932; Sat, 20 Jun 2020 23:36:47 GMT Date: Sat, 20 Jun 2020 23:36:47 +0000 From: Bjarni Ingi Gislason To: mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org Subject: [PATCH] man4/*: srcfix, fix warnings from "mandoc -Tlint" Message-ID: <20200620233647.GA8900@rhi.hi.is> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org Remove superfluous paragraph macros. The output from "nroff" and "groff" is unchanged. ### Examples of warnings: mandoc: fuse.4:244:2: WARNING: skipping paragraph macro: IP empty mandoc: fuse.4:34:2: WARNING: skipping paragraph macro: PP after SH mandoc: lirc.4:68:2: WARNING: skipping paragraph macro: PP after SS mandoc: msr.4:59:2: WARNING: skipping paragraph macro: PP empty Signed-off-by: Bjarni Ingi Gislason --- man4/fuse.4 | 5 ----- man4/lirc.4 | 10 ---------- man4/msr.4 | 1 - man4/st.4 | 3 --- man4/veth.4 | 1 - 5 files changed, 20 deletions(-) diff --git a/man4/fuse.4 b/man4/fuse.4 index 4c40c801a..c1416fb64 100644 --- a/man4/fuse.4 +++ b/man4/fuse.4 @@ -31,7 +31,6 @@ fuse \- Filesystem in Userspace (FUSE) device .B #include .fi .SH DESCRIPTION -.PP This device is the primary interface between the FUSE filesystem driver and a user-space process wishing to provide the filesystem (referred to in the rest of this manual page as the @@ -241,7 +240,6 @@ struct fuse_attr_out { }; .EE .in -.IP .TP .B FUSE_ACCESS .IP @@ -285,7 +283,6 @@ filesystem should validate that the requested are valid for the indicated resource and then send a reply with the following format: .IP -.IP .in +4n .EX struct fuse_open_out { @@ -296,7 +293,6 @@ struct fuse_open_out { .EE .in .IP -.IP The .I fh field is an opaque identifier that the kernel will use to refer @@ -333,7 +329,6 @@ struct fuse_read_in { .EE .in .IP -.IP The requested action is to read up to .I size bytes of the file or directory, starting at diff --git a/man4/lirc.4 b/man4/lirc.4 index 29bbeea34..475fed848 100644 --- a/man4/lirc.4 +++ b/man4/lirc.4 @@ -25,7 +25,6 @@ .SH NAME lirc \- lirc devices .SH DESCRIPTION -.PP The .I /dev/lirc* character devices provide a low-level @@ -65,7 +64,6 @@ receiving and sending is supported, and in which modes, amongst other features. .\" .SS Reading input with the LIRC_MODE_MODE2 mode -.PP In the \fBLIRC_MODE_MODE2 mode\fR, the data returned by .BR read (2) provides 32-bit values representing a space or a pulse duration. @@ -90,7 +88,6 @@ The package reflects a timeout; see the ioctl. .\" .SS Reading input with the LIRC_MODE_SCANCODE mode -.PP In the \fBLIRC_MODE_SCANCODE\fR mode, the data returned by .BR read (2) @@ -100,7 +97,6 @@ is stored in \fIrc_proto\fR. This field has one the values of the \fIenum rc_proto\fR. .\" .SS Writing output with the LIRC_MODE_PULSE mode -.PP The data written to the character device using .BR write (2) is a pulse/space sequence of integer values. @@ -116,7 +112,6 @@ If more data is provided than the hardware can send, the call fails with the error .BR EINVAL . .SS Writing output with the LIRC_MODE_SCANCODE mode -.PP The data written to the character devices must be a single struct \fIlirc_scancode\fR. The \fIscancode\fR and \fIrc_proto\fR fields must @@ -127,7 +122,6 @@ The protocol or scancode is invalid, or the .B lirc device cannot transmit. .SH IOCTL COMMANDS -.PP The LIRC device's ioctl definition is bound by the ioctl function definition of .IR "struct file_operations" , @@ -153,7 +147,6 @@ referred to below as .IR val . .\" .SS Always Supported Commands -.PP \fI/dev/lirc*\fR devices always support the following commands: .TP 4 .BR LIRC_GET_FEATURES " (\fIvoid\fP)" @@ -166,7 +159,6 @@ it is safe to assume it is not a device. .\" .SS Optional Commands -.PP Some .B lirc devices support the commands listed below. @@ -241,7 +233,6 @@ is a number in the range [0,100] which describes the pulse width as a percentage of the total cycle. Currently, no special meaning is defined for 0 or 100, but the values are reserved for future use. -.IP .TP .BR LIRC_GET_MIN_TIMEOUT " (\fIvoid\fP)", " "\ LIRC_GET_MAX_TIMEOUT " (\fIvoid\fP)" @@ -363,7 +354,6 @@ Trying to disable a wide band receiver while carrier reports are active will do nothing. .\" .SH FEATURES -.PP the .B LIRC_GET_FEATURES ioctl returns a bit mask describing features of the driver. diff --git a/man4/msr.4 b/man4/msr.4 index 9feb78a4b..38e4e8e18 100644 --- a/man4/msr.4 +++ b/man4/msr.4 @@ -56,7 +56,6 @@ to load it explicitly before use: $ modprobe msr .EE .in -.PP .SH SEE ALSO Intel Corporation Intel 64 and IA-32 Architectures Software Developer's Manual Volume 3B Appendix B, diff --git a/man4/st.4 b/man4/st.4 index 770ed40e5..151e8b35b 100644 --- a/man4/st.4 +++ b/man4/st.4 @@ -238,7 +238,6 @@ driver. The definitions below are from .IR /usr/include/linux/mtio.h : .SS MTIOCTOP \(em perform a tape operation -.PP This request takes an argument of type .IR "(struct mtop\ *)" . Not all drives support all operations. @@ -686,7 +685,6 @@ the cleaning request. If the pattern is nonzero, the pattern must match the masked sense data byte. .SS MTIOCGET \(em get status -.PP This request takes an argument of type .IR "(struct mtget\ *)" . .PP @@ -815,7 +813,6 @@ This value is set to \-1 when the block number is unknown (e.g., after or .BR MTSEEK ). .SS MTIOCPOS \(em get tape position -.PP This request takes an argument of type .I "(struct mtpos\ *)" and reports the drive's notion of the current tape block number, diff --git a/man4/veth.4 b/man4/veth.4 index 1cc473434..e5d11b2b6 100644 --- a/man4/veth.4 +++ b/man4/veth.4 @@ -98,7 +98,6 @@ NIC statistics: 16: ve_B@ve_A: mtu 1500 qdisc ... .EE .in -.PP .SH "SEE ALSO" .BR clone (2), .BR network_namespaces (7), -- 2.27.0