From: Matthew Wilcox <willy@infradead.org>
To: Bingwu Zhang <xtex@envs.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
Miklos Szeredi <miklos@szeredi.hu>,
"Darrick J. Wong" <djwong@kernel.org>,
Bingwu Zhang <xtex@aosc.io>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-xfs@vger.kernel.org, ~xtex/staging@lists.sr.ht
Subject: Re: [PATCH] Documentation: filesystems: fix two misspells
Date: Wed, 11 Dec 2024 19:58:31 +0000 [thread overview]
Message-ID: <Z1nu50C6grj5th7e@casper.infradead.org> (raw)
In-Reply-To: <20241208035447.162465-2-xtex@envs.net>
On Sun, Dec 08, 2024 at 11:54:47AM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtex@aosc.io>
>
> This fixes two small misspells in the filesystems documentation.
There's a couple of similar ones if you want to submit some bonus
patches:
$ git grep sytem
Documentation/devicetree/bindings/sound/amlogic,axg-sound-card.yaml: Base PLL clocks of audio susbsytem, used to configure base clock
Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml: Base PLL clocks of audio susbsytem, used to configure base clock
Documentation/filesystems/iomap/operations.rst: Races can also happen if the filesytem allows concurrent writes.
drivers/gpu/drm/xe/xe_bo.c: * On successful completion, the object memory will be moved to sytem memory.
fs/freevxfs/vxfs_super.c: * @fc: filesytem context
fs/ocfs2/sysfile.c: * return NULL here so that ocfs2_get_sytem_file_inodes
scripts/spelling.txt:sytem||system
next prev parent reply other threads:[~2024-12-11 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 3:54 [PATCH] Documentation: filesystems: fix two misspells Bingwu Zhang
2024-12-11 17:40 ` Darrick J. Wong
2024-12-11 19:58 ` Matthew Wilcox [this message]
2024-12-13 15:47 ` Jonathan Corbet
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=Z1nu50C6grj5th7e@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=xtex@aosc.io \
--cc=xtex@envs.net \
--cc=~xtex/staging@lists.sr.ht \
/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