From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Don Brace <don.brace@microsemi.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Kevin.Barnett@microchip.com, scott.teel@microchip.com,
Justin.Lindley@microchip.com, scott.benesh@microchip.com,
bader.alisaleh@microchip.com, gerry.morong@microchip.com,
mahesh.rajashekhara@microchip.com
Subject: Re: [PATCH V2 6/6] smartpqi: correct lockup action table
Date: Sat, 24 Aug 2019 11:53:55 +1000 [thread overview]
Message-ID: <20190824015353.owabg7ato6zbxcdf@localhost.localdomain> (raw)
In-Reply-To: <156658019169.6969.9703957231113751364.stgit@brunhilda>
[-- Attachment #1: Type: text/plain, Size: 2530 bytes --]
Hi Don,
As noted in my previous message, I suspect this entire segment (6/6) of
the patch is rendered unnecessary if you revert the introduction of the
.TP tagged paragraph macro immediately prior to the .TS table start
macro in segement 3/6.
Also, it's generally better style-wise (in my opinion!) to use tbl(1) to
achieve columnated output in man pages, rather than trying to use tab
stops for this purpose. I suspect Mr. Kerrisk agrees; while there's no
formal guidance regarding this in man-pages(7), I find 722 lines
matching '^\.TS' in man-pages git HEAD, and only 10 matching
'^\.ta'--and all of those are in timezone-related pages[1], so they
perhaps came in together as part of some sort of import.
This is true even if all tbl(1) ends up doing is setting up tab stops
for you! It is valuable to preserve the semantic content that tbl
macros give us. Recognition of the distinction between semantic
markup and presentational markup has been hard-won in the decades since
the classic Unix toolkit was designed.
Finally, in man-pages project parlance, the change below, to convert
from a tbl-preprocessed table to a hand-crafted one using low-level roff
tab requests and literal tab characters, would probably be characterized
as a "srcfix" if there is no visible change to the page as rendered, and
"ffix" if there is[2].
Regards,
Branden
[1] for the curious: tzfile(5), zdump(8), and zic(8)
[2] https://www.kernel.org/doc/man-pages/patches.html ; see "For trivial
patches..."
At 2019-08-23T12:09:51-0500, Don Brace wrote:
> Reviewed-by: Matt Perricone <matt.perricone@microsemi.com>
> Reviewed-by: Scott Benesh <scott.benesh@microsemi.com>
> Signed-off-by: Don Brace <don.brace@microsemi.com>
> ---
> man4/smartpqi.4 | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/man4/smartpqi.4 b/man4/smartpqi.4
> index 6e2cd1328..43e1d1cb2 100644
> --- a/man4/smartpqi.4
> +++ b/man4/smartpqi.4
> @@ -84,15 +84,15 @@ Specifies the action the driver takes when a controller
> lockup is detected.
> The default action is
> .BR none .
> -.TP
> -.TS
> -l l
> ----
> -l l.
> +.nf
> +.ta 10n +10n
> +
> parameter action
> +--------- ----------------------------
> \fBnone\fP take controller offline only
> \fBreboot\fP reboot the system
> \fBpanic\fP panic the system
> +.fi
> .TP
> .BR expose_ld_first= { 0 | 1 }
> This option enables support for exposing logical devices to OS before physical devices.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-24 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 17:09 [PATCH V2 0/6] smartpqi man page update Don Brace
2019-08-23 17:09 ` [PATCH V2 1/6] smartpqi: fix spelling error Don Brace
2019-08-23 17:09 ` [PATCH V2 2/6] smartpqi: update copyright Don Brace
2019-08-23 17:09 ` [PATCH V2 3/6] smartpqi: add module param expose ld first Don Brace
2019-08-24 1:33 ` G. Branden Robinson
2019-08-23 17:09 ` [PATCH V2 4/6] smartpqi: add module param to hide vsep Don Brace
2019-08-23 17:09 ` [PATCH V2 5/6] smartpqi: add sysfs entries Don Brace
2019-08-23 17:09 ` [PATCH V2 6/6] smartpqi: correct lockup action table Don Brace
2019-08-24 1:53 ` G. Branden Robinson [this message]
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=20190824015353.owabg7ato6zbxcdf@localhost.localdomain \
--to=g.branden.robinson@gmail.com \
--cc=Justin.Lindley@microchip.com \
--cc=Kevin.Barnett@microchip.com \
--cc=bader.alisaleh@microchip.com \
--cc=don.brace@microsemi.com \
--cc=gerry.morong@microchip.com \
--cc=linux-man@vger.kernel.org \
--cc=mahesh.rajashekhara@microchip.com \
--cc=mtk.manpages@gmail.com \
--cc=scott.benesh@microchip.com \
--cc=scott.teel@microchip.com \
/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