From: Randy Dunlap <rdunlap@infradead.org>
To: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Carlos Maiolino <cem@kernel.org>,
David Howells <dhowells@redhat.com>,
Paulo Alcantara <pc@manguebit.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-bcachefs@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com
Subject: Re: [PATCH] fs: doc: Fix typos
Date: Wed, 1 Oct 2025 09:53:40 -0700 [thread overview]
Message-ID: <81c03cb3-5c97-4a6d-bf20-53c5afde2b42@infradead.org> (raw)
In-Reply-To: <20251001083931.44528-1-bhanuseshukumar@gmail.com>
On 10/1/25 1:39 AM, Bhanu Seshu Kumar Valluri wrote:
> Fix typos in doc comments
>
> Signed-off-by: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Note: No change in functionality intended.
>
> Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++---
> Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +-
> fs/netfs/buffered_read.c | 2 +-
> fs/xfs/xfs_linux.h | 2 +-
> include/linux/fs.h | 4 ++--
> 5 files changed, 8 insertions(+), 8 deletions(-)
--
~Randy
prev parent reply other threads:[~2025-10-01 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DrG_H24-pk-ha8vkOEHoZYVXyMFA60c_g4l7cZX4Z7lnKQIM4FjdI_qS-UIpFxa-t7T_JDAOSqKjew7M0wmYYw==@protonmail.internalid>
2025-10-01 8:39 ` [PATCH] fs: doc: Fix typos Bhanu Seshu Kumar Valluri
2025-10-01 9:36 ` David Howells
2025-10-01 12:02 ` Carlos Maiolino
2025-10-01 13:49 ` Bhanu Seshu Kumar Valluri
2025-10-03 15:52 ` Carlos Maiolino
2025-10-04 4:31 ` Bhanu Seshu Kumar Valluri
2025-10-04 4:33 ` Bhanu Seshu Kumar Valluri
2025-10-01 16:53 ` Randy Dunlap [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=81c03cb3-5c97-4a6d-bf20-53c5afde2b42@infradead.org \
--to=rdunlap@infradead.org \
--cc=bhanuseshukumar@gmail.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=corbet@lwn.net \
--cc=david.hunter.linux@gmail.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=skhan@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).