linux-kernel - Re: [PATCH] docs: filesystems: fix typo in docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 09 Feb 2024 07:21:37 -0700
From: Jonathan Corbet <corbet@....net>
To: Christian Brauner <brauner@...nel.org>, Vincenzo Mezzela
 <vincenzo.mezzela@...il.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 skhan@...uxfoundation.org
Subject: Re: [PATCH] docs: filesystems: fix typo in docs

Christian Brauner <brauner@...nel.org> writes:

> On Thu, Feb 08, 2024 at 05:20:32PM +0100, Vincenzo Mezzela wrote:
>> This patch resolves a spelling error in the filesystem documentation.
>> 
>> It is submitted as part of my application to the "Linux Kernel Bug
>> Fixing Spring Unpaid 2024" mentorship program of the Linux Kernel
>> Foundation.
>> 
>> Signed-off-by: Vincenzo Mezzela <vincenzo.mezzela@...il.com>
>> ---
>>  Documentation/filesystems/files.rst | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/Documentation/filesystems/files.rst b/Documentation/filesystems/files.rst
>> index 9e38e4c221ca..eb770f891b27 100644
>> --- a/Documentation/filesystems/files.rst
>> +++ b/Documentation/filesystems/files.rst
>> @@ -116,7 +116,7 @@ before and after the reference count increment. This pattern can be seen
>>  in get_file_rcu() and __files_get_rcu().
>>  
>>  In addition, it isn't possible to access or check fields in struct file
>> -without first aqcuiring a reference on it under rcu lookup. Not doing
>> +without first acquiring a reference on it under rcu lookup. Not doing
>
> I stared at this for way too long to figure out that there's actually a
> spelling mistake in there. Thanks! I've snagged it. Jon, let me know if
> you prefer to take it.

I'd applied it too - sorry, he sent two and I replied once to the other
one, which you didn't get.  I can drop my copy.

Thanks,

jon