aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/mpr
diff options
context:
space:
mode:
authorWarner Losh <imp@FreeBSD.org>2023-07-20 23:16:04 +0000
committerWarner Losh <imp@FreeBSD.org>2023-07-20 23:18:28 +0000
commit59dc489a7e034674c3f52c56c95851bf31dc790b (patch)
tree8bebe926c3547bda9b47d1467a3c2ba64afdcc8f /sys/dev/mpr
parentba2f531f816a6bc1ef5f2cba4a329ff7bdbec0f3 (diff)
Diffstat (limited to 'sys/dev/mpr')
-rw-r--r--sys/dev/mpr/mpr_sas.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/dev/mpr/mpr_sas.c b/sys/dev/mpr/mpr_sas.c
index dd630d212b7f..06dbed57dbac 100644
--- a/sys/dev/mpr/mpr_sas.c
+++ b/sys/dev/mpr/mpr_sas.c
@@ -2767,13 +2767,13 @@ mprsas_scsiio_complete(struct mpr_softc *sc, struct mpr_command *cm)
* count by returning CAM_REQUEUE_REQ. Unfortunately, if
* we hit a persistent drive problem that returns one of
* these error codes, we would retry indefinitely. So,
- * return CAM_REQ_CMP_ERROR so that we decrement the retry
+ * return CAM_REQ_CMP_ERR so that we decrement the retry
* count and avoid infinite retries. We're taking the
* potential risk of flagging false failures in the event
* of a topology-related error (e.g. a SAS expander problem
* causes a command addressed to a drive to fail), but
* avoiding getting into an infinite retry loop. However,
- * if we get them while were moving a device, we should
+ * if we get them while were removing a device, we should
* fail the request as 'not there' because the device
* is effectively gone.
*/