From: Moktar sellami <smokthar925@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Cc: linux-cxl@vger.kernel.org, linux-doc@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Gregory Price <gourry@gourry.net>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH] Documentation/driver-api: Fix typo error in cxl
Date: Mon, 1 Sep 2025 00:07:26 +0100 [thread overview]
Message-ID: <c6158f58-7a62-4df3-b025-4fe9f33c4d16@gmail.com> (raw)
In-Reply-To: <87iki53gfb.fsf@trenco.lwn.net>
On 8/29/25 23:35, Jonathan Corbet wrote:
> Moktar SELLAMI <smokthar925@gmail.com> writes:
>
>> Fixed Typo in the driver-api/cxl/devices/devices.rst
>>
>> functionalty -> functionality
>>
>> Signed-off-by: Moktar SELLAMI <smokthar925@gmail.com>
>> ---
>> Documentation/driver-api/cxl/devices/device-types.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> 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).
> This one was fixed a while back, so this patch is not needed. It is
> always a good idea to check linux-next when considering changes of this
> type.
>
> Thanks,
>
> jon
Thank you for the clarification and for pointing me to linux-next. i
will try to come up with an other patch thank u.
Moktar
next prev parent reply other threads:[~2025-08-31 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:41 [PATCH] Documentation/driver-api: Fix typo error in cxl Moktar SELLAMI
2025-08-19 11:28 ` Jonathan Cameron
2025-08-19 17:23 ` Randy Dunlap
2025-08-29 22:35 ` Jonathan Corbet
2025-08-31 23:07 ` Moktar sellami [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-16 18:30 rakuram
2025-08-16 20:20 ` Randy Dunlap
2025-08-17 17:04 ` Gregory Price
2025-08-17 17:50 ` rakuram
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=c6158f58-7a62-4df3-b025-4fe9f33c4d16@gmail.com \
--to=smokthar925@gmail.com \
--cc=alison.schofield@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).