Skip to content

Commit f7f5074

Browse files
Shen Lichuanweiny2
authored andcommitted
nvdimm: Correct some typos in comments
Fixed some confusing typos that were currently identified with codespell, the details are as follows: -in the code comments: drivers/nvdimm/nd_virtio.c:100: repsonse ==> response drivers/nvdimm/pfn_devs.c:542: namepace ==> namespace drivers/nvdimm/pmem.c:319: reenable ==> re-enable Signed-off-by: Shen Lichuan <shenlichuan@vivo.com> Reviewed-by: Dave Jiang <dave.jiang@intel.com> Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com> Link: https://patch.msgid.link/20240926075700.10122-1-shenlichuan@vivo.com Signed-off-by: Ira Weiny <ira.weiny@intel.com>
1 parent 50643bb commit f7f5074

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

drivers/nvdimm/nd_virtio.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ static int virtio_pmem_flush(struct nd_region *nd_region)
9797
dev_info(&vdev->dev, "failed to send command to virtio pmem device\n");
9898
err = -EIO;
9999
} else {
100-
/* A host repsonse results in "host_ack" getting called */
100+
/* A host response results in "host_ack" getting called */
101101
wait_event(req_data->host_acked, req_data->done);
102102
err = le32_to_cpu(req_data->resp.ret);
103103
}

drivers/nvdimm/pfn_devs.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -539,7 +539,7 @@ int nd_pfn_validate(struct nd_pfn *nd_pfn, const char *sig)
539539

540540
if (!nd_pfn->uuid) {
541541
/*
542-
* When probing a namepace via nd_pfn_probe() the uuid
542+
* When probing a namespace via nd_pfn_probe() the uuid
543543
* is NULL (see: nd_pfn_devinit()) we init settings from
544544
* pfn_sb
545545
*/

drivers/nvdimm/pmem.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -316,7 +316,7 @@ static long pmem_dax_direct_access(struct dax_device *dax_dev,
316316
* range, filesystem turns the normal pwrite to a dax_recovery_write.
317317
*
318318
* The recovery write consists of clearing media poison, clearing page
319-
* HWPoison bit, reenable page-wide read-write permission, flush the
319+
* HWPoison bit, re-enable page-wide read-write permission, flush the
320320
* caches and finally write. A competing pread thread will be held
321321
* off during the recovery process since data read back might not be
322322
* valid, and this is achieved by clearing the badblock records after

0 commit comments

Comments
 (0)