nvdimm: Correct some typos in comments

JIRA: https://issues.redhat.com/browse/RHEL-96835

commit f7f5074
Author: Shen Lichuan <shenlichuan@vivo.com>
Date:   Thu Sep 26 15:57:00 2024 +0800

    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>

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>

Author: JeffMoyer

drivers/nvdimm/nd_virtio.c

@@ -88,7 +88,7 @@ static int virtio_pmem_flush(struct nd_region *nd_region)
 		dev_info(&vdev->dev, "failed to send command to virtio pmem device\n");
 		err = -EIO;
 	} else {
-		/* A host repsonse results in "host_ack" getting called */
+		/* A host response results in "host_ack" getting called */
 		wait_event(req_data->host_acked, req_data->done);
 		err = le32_to_cpu(req_data->resp.ret);
 	}

drivers/nvdimm/pfn_devs.c

@@ -539,7 +539,7 @@ int nd_pfn_validate(struct nd_pfn *nd_pfn, const char *sig)
 
 	if (!nd_pfn->uuid) {
 		/*
-		 * When probing a namepace via nd_pfn_probe() the uuid
+		 * When probing a namespace via nd_pfn_probe() the uuid
 		 * is NULL (see: nd_pfn_devinit()) we init settings from
 		 * pfn_sb
 		 */

drivers/nvdimm/pmem.c

@@ -316,7 +316,7 @@ static long pmem_dax_direct_access(struct dax_device *dax_dev,
  * range, filesystem turns the normal pwrite to a dax_recovery_write.
  *
  * The recovery write consists of clearing media poison, clearing page
- * HWPoison bit, reenable page-wide read-write permission, flush the
+ * HWPoison bit, re-enable page-wide read-write permission, flush the
  * caches and finally write.  A competing pread thread will be held
  * off during the recovery process since data read back might not be
  * valid, and this is achieved by clearing the badblock records after