mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
	ira.weiny@intel.com, dave@stgolabs.net,
	Jonathan.Cameron@huawei.com, ming.li@zohomail.com
Cc: linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
	darren.kenny@oracle.com
Subject: Re: [PATCH] cxl/Documentation: Fix typo in sysfs write_bandwidth attribute path
Date: Fri, 16 May 2025 07:27:16 -0700	[thread overview]
Message-ID: <3bdf2d89-8bde-4c54-89b2-77f170af6159@intel.com> (raw)
In-Reply-To: <20250516103855.3820882-1-alok.a.tiwari@oracle.com>



On 5/16/25 3:38 AM, Alok Tiwari wrote:
> Fix a typo in the sysfs documentation for the CXL "write_bandwidth"
> attribute path. The attribute was incorrectly documented as write_banwidth.
> Update it to the correct write_bandwidth to align with the actual
> implementation.
> 
> Fixes: c20eaf44113e ("cxl/region: Add sysfs attribute for locality attributes of CXL regions")
> Cc: stable@vger.kernel.org
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>

Thanks! I'll probably drop the fixes tag and the cc stable tag since it doesn't impact a running kernel.

Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
>  Documentation/ABI/testing/sysfs-bus-cxl | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-cxl b/Documentation/ABI/testing/sysfs-bus-cxl
> index 99bb3faf7a0e..eca1054ca168 100644
> --- a/Documentation/ABI/testing/sysfs-bus-cxl
> +++ b/Documentation/ABI/testing/sysfs-bus-cxl
> @@ -572,7 +572,7 @@ Description:
>  
>  
>  What:		/sys/bus/cxl/devices/regionZ/accessY/read_bandwidth
> -		/sys/bus/cxl/devices/regionZ/accessY/write_banwidth
> +		/sys/bus/cxl/devices/regionZ/accessY/write_bandwidth
>  Date:		Jan, 2024
>  KernelVersion:	v6.9
>  Contact:	linux-cxl@vger.kernel.org


  reply	other threads:[~2025-05-16 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 10:38 Alok Tiwari
2025-05-16 14:27 ` Dave Jiang [this message]
2025-05-16 14:28 ` Dave Jiang

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=3bdf2d89-8bde-4c54-89b2-77f170af6159@intel.com \
    --to=dave.jiang@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=darren.kenny@oracle.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.li@zohomail.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

all inboxes | Powered by JetHome®