linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Ranganath V N <vnranganath.20@gmail.com>,
	corbet@lwn.net, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, alim.akhtar@samsung.com,
	dave@stgolabs.net, rafael@kernel.org,
	linux-kernel-mentees@vger.kernel.org, skhan@linuxfoundation.org,
	vishal.l.verma@intel.com
Subject: Re: [PATCH] Documentation: Fix driver-api typos
Date: Thu, 14 Aug 2025 09:06:58 -0700	[thread overview]
Message-ID: <18b2a030-f607-4a6c-bd55-b704a06c6948@intel.com> (raw)
In-Reply-To: <20250814114245.16399-1-vnranganath.20@gmail.com>



On 8/14/25 4:42 AM, Ranganath V N wrote:
> Corrected a few spelling mistakes
> 
> - functionalty ==> functionality
> in Documentation/driver-api/cxl/devices/device-types.rst
> 
> - adjascent ==> adjacent
> in Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> 
> - succeessful ==> successful
> in Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> 
> Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>

Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
>  Documentation/driver-api/cxl/devices/device-types.rst           | 2 +-
>  .../cxl/platform/example-configurations/one-dev-per-hb.rst      | 2 +-
>  Documentation/driver-api/thermal/exynos_thermal_emulation.rst   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/driver-api/cxl/devices/device-types.rst b/Documentation/driver-api/cxl/devices/device-types.rst
> index 923f5d89bc04..7f69dfa4509b 100644
> --- a/Documentation/driver-api/cxl/devices/device-types.rst
> +++ b/Documentation/driver-api/cxl/devices/device-types.rst
> @@ -22,7 +22,7 @@ The basic interaction protocol, similar to PCIe configuration mechanisms.
>  Typically used for initialization, configuration, and I/O access for anything
>  other than memory (CXL.mem) or cache (CXL.cache) operations.
>  
> -The Linux CXL driver exposes access to .io functionalty via the various sysfs
> +The Linux CXL driver exposes access to .io functionality via the various sysfs
>  interfaces and /dev/cxl/ devices (which exposes direct access to device
>  mailboxes).
>  
> diff --git a/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst b/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> index aebda0eb3e17..a4c3fb51ea7d 100644
> --- a/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> +++ b/Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
> @@ -10,7 +10,7 @@ has a single CXL memory expander with a 4GB of memory.
>  Things to note:
>  
>  * Cross-Bridge interleave is not being used.
> -* The expanders are in two separate but adjascent memory regions.
> +* The expanders are in two separate but adjacent memory regions.
>  * This CEDT/SRAT describes one node per device
>  * The expanders have the same performance and will be in the same memory tier.
>  
> diff --git a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> index c21d10838bc5..f77d27c25ce2 100644
> --- a/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> +++ b/Documentation/driver-api/thermal/exynos_thermal_emulation.rst
> @@ -32,7 +32,7 @@ Exynos emulation mode requires synchronous of value changing and
>  enabling. It means when you want to update the any value of delay or
>  next temperature, then you have to enable emulation mode at the same
>  time. (Or you have to keep the mode enabling.) If you don't, it fails to
> -change the value to updated one and just use last succeessful value
> +change the value to updated one and just use last successful value
>  repeatedly. That's why this node gives users the right to change
>  termerpature only. Just one interface makes it more simply to use.
>  


  parent reply	other threads:[~2025-08-14 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 11:42 [PATCH] Documentation: Fix driver-api typos Ranganath V N
2025-08-14 15:56 ` Randy Dunlap
2025-08-14 16:06 ` Dave Jiang [this message]
2025-08-14 16:08 ` Alison Schofield
2025-08-14 18:43   ` [PATCH v2] " Ranganath V N
2025-08-14 18:52     ` Randy Dunlap
2025-08-14 19:57     ` Jonathan Corbet

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=18b2a030-f607-4a6c-bd55-b704a06c6948@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=corbet@lwn.net \
    --cc=dave@stgolabs.net \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=vishal.l.verma@intel.com \
    --cc=vnranganath.20@gmail.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;
as well as URLs for NNTP newsgroup(s).