From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Akiyoshi Kurita <weibu@redadmin.org>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] Documentation: f2fs: Fix typos in sysfs-fs-f2fs
Date: Sun, 28 Sep 2025 17:30:34 +0800 [thread overview]
Message-ID: <1a931cfa-0846-488b-ab1a-f3dee33e1d21@kernel.org> (raw)
In-Reply-To: <20250926180134.35329-1-weibu@redadmin.org>
On 9/27/2025 2:01 AM, Akiyoshi Kurita wrote:
> Fix two spelling mistakes in the f2fs sysfs ABI documentation:
> - deivces -> devices
> - substracting -> subtracting
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-09-28 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 18:01 [f2fs-dev] [PATCH] Documentation: f2fs: Fix typos in sysfs-fs-f2fs Akiyoshi Kurita
2025-09-28 9:30 ` Chao Yu via Linux-f2fs-devel [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=1a931cfa-0846-488b-ab1a-f3dee33e1d21@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=weibu@redadmin.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).