From: Alejandro Colomar <alx@kernel.org>
To: Don Brace <don.brace@microchip.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v4 1/5] smartpqi: add module parameter ctrl_ready_timeout
Date: Tue, 3 Oct 2023 02:24:43 +0200 [thread overview]
Message-ID: <ZRtfS8DIxlqNN-XH@debian> (raw)
In-Reply-To: <20231002195404.153182-2-don.brace@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
Hi Don,
On Mon, Oct 02, 2023 at 02:54:00PM -0500, Don Brace wrote:
> Allow user to change the length of time that the driver
> will wait for the controller to become ready.
>
> Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
> Reviewed-by: Scott Teel <scott.teel@microchip.com>
> Reviewed-by: Mike McGowen <mike.mcgowen@microchip.com>
> Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
> Signed-off-by: Don Brace <don.brace@microchip.com>
> ---
> man4/smartpqi.4 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man4/smartpqi.4 b/man4/smartpqi.4
> index 32f9240e37f2..5ccbbe1c4ef1 100644
> --- a/man4/smartpqi.4
> +++ b/man4/smartpqi.4
> @@ -17,6 +17,7 @@ smartpqi \- Microchip Smart Storage SCSI driver
> .RB [ expose_ld_first= { 0 | 1 }]
> .RB [ hide_vsep= { 0 | 1 }]
> .RB [ disable_managed_interrupts= { 0 | 1 }]
> +.RB [ ctrl_ready_timeout= { 0 | 30-1800 }]
> .YS
> .SH DESCRIPTION
> .B smartpqi
> @@ -107,6 +108,11 @@ Disables driver utilization of Linux kernel managed interrupts for controllers.
> The managed interrupts feature automatically distributes interrupts
> to all available CPUs and assigns SMP affinity.
> The default value is 0 (managed interrupts enabled).
> +.TP
> +.BR ctrl_ready_timeout= { 0 | 30-1800 }
> +This option specifies the timeout in seconds for the driver to wait
> +for controller ready. The valid range is 0 or 30-1800. The default value
How about "for the controller to be ready"?
Also, please break lines after period (per "semantic newlines"
guidelines in man-pages(7)).
$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
Use semantic newlines
In the source of a manual page, new sentences should be started
on new lines, long sentences should be split into lines at
clause breaks (commas, semicolons, colons, and so on), and long
clauses should be split at phrase boundaries. This convention,
sometimes known as "semantic newlines", makes it easier to see
the effect of patches, which often operate at the level of in‐
dividual sentences, clauses, or phrases.
Regarding ranges, please say 0 or [30, 1800], to use standard syntax.
Thanks,
Alex
> +is 0, which causes the driver to use a timeout of 180 seconds.
> .SH FILES
> .SS Device nodes
> Logical drives are accessed via the SCSI disk driver
> --
> 2.42.0.296.g493f462273
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-03 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:53 [PATCH v4 0/5] smartpqi man page updates Don Brace
2023-10-02 19:54 ` [PATCH v4 1/5] smartpqi: add module parameter ctrl_ready_timeout Don Brace
2023-10-03 0:24 ` Alejandro Colomar [this message]
2023-10-02 19:54 ` [PATCH v4 2/5] smartpqi: update FILES section Don Brace
2023-10-02 19:54 ` [PATCH v4 3/5] smartpqi: update host attribute descriptions Don Brace
2023-10-03 0:28 ` Alejandro Colomar
2023-10-02 19:54 ` [PATCH v4 4/5] smartpqi: add host attributes Don Brace
2023-10-02 19:54 ` [PATCH v4 5/5] smartpqi: add device attributes Don Brace
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=ZRtfS8DIxlqNN-XH@debian \
--to=alx@kernel.org \
--cc=don.brace@microchip.com \
--cc=linux-man@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).