All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Yahu YH12 Gao <gaoyh12@lenovo.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Subject: Re: [PATCH V2] drivers/dax: Fix typo in comment
Date: Mon, 13 Apr 2026 16:16:56 +0100	[thread overview]
Message-ID: <20260413161656.00003403@huawei.com> (raw)
In-Reply-To: <OSNPR03MB95383CB4853CB4CD18C2A376DF5CA@OSNPR03MB9538.apcprd03.prod.outlook.com>

On Sun, 5 Apr 2026 03:45:43 +0000
Yahu YH12 Gao <gaoyh12@lenovo.com> wrote:

> Fix a typo in dax_copy_to_iter where "vfs_red" should be "vfs_read".
> 
> Signed-off-by: Yahu Gao <gaoyh12@lenovo.com>
> 

Should have change log.  Format as:

---

v2: What changed.


(Though given you've sent this out already just reply here to say what changed)

> diff --git a/drivers/dax/super.c b/drivers/dax/super.c
> index c00b9dff4a06..e32db0eba9c1 100644
> --- a/drivers/dax/super.c
> +++ b/drivers/dax/super.c
> @@ -192,7 +192,7 @@ size_t dax_copy_to_iter(struct dax_device *dax_dev, pgoff_t pgoff, void *addr,
> 
>         /*
>          * The userspace address for the memory copy has already been validated
> -        * via access_ok() in vfs_red, so use the 'no check' version to bypass
> +        * via access_ok() in vfs_read, so use the 'no check' version to bypass
>          * the HARDENED_USERCOPY overhead.
>          */
>         if (test_bit(DAXDEV_NOMC, &dax_dev->flags))
> --
> 2.47.3
> 


  reply	other threads:[~2026-04-13 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05  3:45 [PATCH V2] drivers/dax: Fix typo in comment Yahu YH12 Gao
2026-04-13 15:16 ` Jonathan Cameron [this message]
2026-04-14  2:15   ` [External] " Yahu YH12 Gao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260413161656.00003403@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=gaoyh12@lenovo.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.