public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Brace <don.brace@microchip.com>
To: <alx@kernel.org>
Cc: <linux-man@vger.kernel.org>
Subject: [PATCH v4 2/5] smartpqi: update FILES section
Date: Mon, 2 Oct 2023 14:54:01 -0500	[thread overview]
Message-ID: <20231002195404.153182-3-don.brace@microchip.com> (raw)
In-Reply-To: <20231002195404.153182-1-don.brace@microchip.com>

Minor description changes for Device nodes.

Change "Logical drives" to "Disk drives".

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 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man4/smartpqi.4 b/man4/smartpqi.4
index 5ccbbe1c4ef1..34864e60755b 100644
--- a/man4/smartpqi.4
+++ b/man4/smartpqi.4
@@ -115,7 +115,7 @@ for controller ready. The valid range is 0 or 30-1800. The default value
 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
+Disk drives are accessed via the SCSI disk driver
 .RI ( sd ),
 tape drives via the SCSI tape driver
 .RI ( st ),
-- 
2.42.0.296.g493f462273


  parent reply	other threads:[~2023-10-02 19:51 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
2023-10-02 19:54 ` Don Brace [this message]
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=20231002195404.153182-3-don.brace@microchip.com \
    --to=don.brace@microchip.com \
    --cc=alx@kernel.org \
    --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