linux-kernel - Re: [PATCH v1] nvdimm: Correct some typos in comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fe8bc21c-b684-4a51-a1c4-2b58412a38d1@intel.com>
Date: Thu, 26 Sep 2024 08:15:16 -0700
From: Dave Jiang <dave.jiang@...el.com>
To: Shen Lichuan <shenlichuan@...o.com>, dan.j.williams@...el.com,
 vishal.l.verma@...el.com, ira.weiny@...el.com, pankaj.gupta.linux@...il.com
Cc: nvdimm@...ts.linux.dev, virtualization@...ts.linux.dev,
 linux-kernel@...r.kernel.org, opensource.kernel@...o.com
Subject: Re: [PATCH v1] nvdimm: Correct some typos in comments



On 9/26/24 12:57 AM, Shen Lichuan wrote:
> 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@...o.com>

Reviewed-by: Dave Jiang <dave.jiang@...el.com>

> ---
>  drivers/nvdimm/nd_virtio.c | 2 +-
>  drivers/nvdimm/pfn_devs.c  | 2 +-
>  drivers/nvdimm/pmem.c      | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/nvdimm/nd_virtio.c b/drivers/nvdimm/nd_virtio.c
> index f55d60922b87..c3f07be4aa22 100644
> --- a/drivers/nvdimm/nd_virtio.c
> +++ b/drivers/nvdimm/nd_virtio.c
> @@ -97,7 +97,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);
>  	}
> diff --git a/drivers/nvdimm/pfn_devs.c b/drivers/nvdimm/pfn_devs.c
> index 586348125b61..cfdfe0eaa512 100644
> --- a/drivers/nvdimm/pfn_devs.c
> +++ b/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
>  		 */
> diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
> index 210fb77f51ba..d81faa9d89c9 100644
> --- a/drivers/nvdimm/pmem.c
> +++ b/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