From: Dave Jiang <dave.jiang@intel.com>
To: Yahu YH12 Gao <gaoyh12@lenovo.com>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>
Cc: "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] drivers/dax: Fix typo in comment
Date: Mon, 6 Apr 2026 08:23:03 -0700 [thread overview]
Message-ID: <fb8dbdce-36a3-40a3-8f01-09e59b4fbfc2@intel.com> (raw)
In-Reply-To: <OSNPR03MB95389421960C592713DD923FDF5CA@OSNPR03MB9538.apcprd03.prod.outlook.com>
On 4/4/26 8:19 PM, Yahu YH12 Gao wrote:
> Fix a typo in dax_copy_to_iter where "vfs_red" should be "vfs_read".
>
> Signed-off-by: Yahu Gao mailto:gaoyh12@lenovo.com
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
>
> 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
>
prev parent reply other threads:[~2026-04-06 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 3:19 [PATCH] drivers/dax: Fix typo in comment Yahu YH12 Gao
2026-04-06 15:23 ` Dave Jiang [this message]
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=fb8dbdce-36a3-40a3-8f01-09e59b4fbfc2@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox