linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Gou Hao <gouhao@uniontech.com>
Cc: cem@kernel.org, corbet@lwn.net, linux-xfs@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	gouhaojake@163.com, guanwentao@uniontech.com
Subject: Re: [PATCH] xfs-doc: Fix typo error
Date: Tue, 4 Nov 2025 02:57:09 -0800	[thread overview]
Message-ID: <aQncBRi8WPh7hmqg@infradead.org> (raw)
In-Reply-To: <20251104093406.9135-1-gouhao@uniontech.com>

On Tue, Nov 04, 2025 at 05:34:06PM +0800, Gou Hao wrote:
> online fsck may take longer than offline fsck...

The o in online should be capitalized.

Otherwise looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>


  reply	other threads:[~2025-11-04 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  9:34 [PATCH] xfs-doc: Fix typo error Gou Hao
2025-11-04 10:57 ` Christoph Hellwig [this message]
2025-11-04 16:56 ` Darrick J. Wong
2025-11-05  1:35 ` [PATCH V2] " Gou Hao
2025-11-10 19:50   ` 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=aQncBRi8WPh7hmqg@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gouhao@uniontech.com \
    --cc=gouhaojake@163.com \
    --cc=guanwentao@uniontech.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.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).