From: Kent Overstreet <kent.overstreet@linux.dev>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Sahil Chandna <chandna.linuxkernel@gmail.com>,
corbet@lwn.net, linux-doc@vger.kernel.org, tj@kernel.org,
cem@kernel.org, linux-bcachefs@vger.kernel.org,
cgroups@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] Documentation: Fix documentation typos
Date: Thu, 21 Aug 2025 17:34:53 -0400 [thread overview]
Message-ID: <23de3jgp44vih5g6hjgc2ji6momi5t3w7rfkm5mgtajicbbg7a@7r5hgt5e7eir> (raw)
In-Reply-To: <4cae933a-d171-48aa-a854-b4323d10b347@infradead.org>
On Thu, Aug 21, 2025 at 12:09:57PM -0700, Randy Dunlap wrote:
>
>
> On 8/21/25 11:51 AM, Sahil Chandna wrote:
> > Fix several spelling mistakes in documentation:
> >
> > - Availablity -> Availability
> > - heirarchy -> hierarchy
> > - maping -> mapping
> > Findings are based on v6.17-rc2.
> >
> > Signed-off-by: Sahil Chandna <chandna.linuxkernel@gmail.com>
> > ---
> > Documentation/admin-guide/cgroup-v2.rst | 2 +-
> > Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++---
> > Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +-
> > 3 files changed, 5 insertions(+), 5 deletions(-)
> >
>
> Looks good, although there was just another patch that also fixed the maping/mapping
> spelling for XFS.
>
> And various maintainers might request that you split the patch up by
> subsystem/filesystem (i.e., 3 patches here) unless Jon merges it as is.
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
I'll take the bcachefs patch if it's split up.
prev parent reply other threads:[~2025-08-21 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 18:51 [PATCH] Documentation: Fix documentation typos Sahil Chandna
2025-08-21 19:09 ` Randy Dunlap
2025-08-21 21:34 ` Kent Overstreet [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=23de3jgp44vih5g6hjgc2ji6momi5t3w7rfkm5mgtajicbbg7a@7r5hgt5e7eir \
--to=kent.overstreet@linux.dev \
--cc=cem@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chandna.linuxkernel@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tj@kernel.org \
/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).