nvme: Fix typos
Subsystems (3)
PATCH v2 1/1 nvme: Fix typos
From: Bjorn Helgaas <[email protected]>
Fix typos in comments.
---
v1: https://lore.kernel.org/r/[email protected]
This v2 based on nvme/nvme-6.17 (e97c0040215f ("nvme-auth: remove unneeded semicolon"))
Changes from v1:
- Drop drivers/nvme/host/apple.c fix; already fixed by 164c187d25b6 ("nvme: fix multiple spelling and grammar issues in host drivers")
- Drop hunks from drivers/nvme/host/fc.c; also fixed by 164c187d25b6
- Drop drivers/nvme/host/pci.c nvme_setup_io_queues() fix; the comment added by e4b9852a0f4a ("nvme-pci: fix multiple races in nvme_setup_io_queues") needs more grammatical work than I can do to be intelligible; authors cc'd
- Drop drivers/nvme/host/rdma.c fix; also fixed by 164c187d25b6
- Add Chaitanya's Reviewed-by since I only dropped hunks, nothing new added
drivers/nvme/host/fc.c | 4 ++-- drivers/nvme/host/tcp.c | 2 +- drivers/nvme/target/fc.c | 6 +++--- drivers/nvme/target/rdma.c | 6 +++--- 4 files changed, 9 insertions(+), 9 deletions(-)
drivers/nvme/host/fc.c +2 -2
@@ -1363,7 +1363,7 @@ nvme_fc_disconnect_assoc_done(struct nvmefc_ls_req *lsreq, int status)* down, and the related FC-NVME Association ID and Connection IDs * become invalid. * -* The behavior of the fc-nvme initiator is such that it's +* The behavior of the fc-nvme initiator is such that its * understanding of the association and connections will implicitly * be torn down. The action is implicit as it may be due to a loss of * connectivity with the fc-nvme target, so you may never get a
@@ -2777,7 +2777,7 @@ nvme_fc_queue_rq(struct blk_mq_hw_ctx *hctx,* as WRITE ZEROES will return a non-zero rq payload_bytes yet * there is no actual payload to be transferred. * To get it right, key data transmission on there being 1 or -* more physical segments in the sg list. If there is no +* more physical segments in the sg list. If there are no * physical segments, there is no payload. */ if (blk_rq_nr_phys_segments (rq)) {
drivers/nvme/host/tcp.c +1 -1
@@ -2179,7 +2179,7 @@ static int nvme_tcp_configure_io_queues(struct nvme_ctrl *ctrl, bool new)/* * Only start IO queues for which we have allocated the tagset -* and limitted it to the available queues. On reconnects, the +* and limited it to the available queues. On reconnects, the * queue number might have changed. */ nr_queues =min (ctrl->tagset->nr_hw_queues +1 , ctrl->queue_count);
drivers/nvme/target/fc.c +3 -3
@@ -459,7 +459,7 @@ nvmet_fc_disconnect_assoc_done(struct nvmefc_ls_req *lsreq, int status)* down, and the related FC-NVME Association ID and Connection IDs * become invalid. * -* The behavior of the fc-nvme target is such that it's +* The behavior of the fc-nvme target is such that its * understanding of the association and connections will implicitly * be torn down. The action is implicit as it may be due to a loss of * connectivity with the fc-nvme host, so the target may never get a
@@ -2313,7 +2313,7 @@ nvmet_fc_transfer_fcp_data(struct nvmet_fc_tgtport *tgtport, ret = tgtport->ops->fcp_op (&tgtport->fc_target_port, fod->fcpreq);if (ret) {/* -* should be ok to set w/o lock as its in the thread of +* should be ok to set w/o lock as it's in the thread of * execution (not an async timer routine) and doesn't * contend with any clearing action */
@@ -2629,7 +2629,7 @@ nvmet_fc_handle_fcp_rqst(struct nvmet_fc_tgtport *tgtport,* and the api of the FC LLDD which may issue a hw command to send the * response, but the LLDD may not get the hw completion for that command * and upcall the nvmet_fc layer before a new command may be -* asynchronously received - its possible for a command to be received +* asynchronously received - it's possible for a command to be received * before the LLDD and nvmet_fc have recycled the job structure. It gives * the appearance of more commands received than fits in the sq. * To alleviate this scenario, a temporary queue is maintained in the
drivers/nvme/target/rdma.c +3 -3
@@ -1731,7 +1731,7 @@ static void nvmet_rdma_queue_connect_fail(struct rdma_cm_id *cm_id,* We registered an ib_client to handle device removal for queues, * so we only need to handle the listening port cm_ids. In this case * we nullify the priv to prevent double cm_id destruction and destroying -* the cm_id implicitely by returning a non-zero rc to the callout. +* the cm_id implicitly by returning a non-zero rc to the callout. */ static int nvmet_rdma_device_removal (struct rdma_cm_id *cm_id,struct nvmet_rdma_queue *queue)
@@ -1742,7 +1742,7 @@ static int nvmet_rdma_device_removal(struct rdma_cm_id *cm_id,/* * This is a queue cm_id. we have registered * an ib_client to handle queues removal -* so don't interfear and just return. +* so don't interfere and just return. */ return 0 ; }
@@ -1760,7 +1760,7 @@ static int nvmet_rdma_device_removal(struct rdma_cm_id *cm_id,/* * We need to return 1 so that the core will destroy -* it's own ID. What a great API design.. +* its own ID. What a great API design.. */ return 1 ; }
Signature · 1 line
2.43.0
Christoph Hellwig
maintainerThanks, I've added the patch and already sent it on to Jens with the current nvme pull request.