From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Charles Han <hanchunchao@inspur.com>, <corbet@lwn.net>,
<djwong@kernel.org>, <dchinner@redhat.com>,
<allison.henderson@oracle.com>, <bhelgaas@google.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: xfs: Remove repeated word in comments
Date: Wed, 20 Sep 2023 07:17:31 +0700 [thread overview]
Message-ID: <ZQo6G5Z2v1Tk6ShQ@debian.me> (raw)
In-Reply-To: <20230918071905.296081-1-hanchunchao@inspur.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Mon, Sep 18, 2023 at 03:19:05PM +0800, Charles Han wrote:
> diff --git a/Documentation/filesystems/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs-online-fsck-design.rst
> index 1625d1131093..a0678101a7d0 100644
> --- a/Documentation/filesystems/xfs-online-fsck-design.rst
> +++ b/Documentation/filesystems/xfs-online-fsck-design.rst
> @@ -1585,7 +1585,7 @@ The transaction sequence looks like this:
> 2. The second transaction contains a physical update to the free space btrees
> of AG 3 to release the former BMBT block and a second physical update to the
> free space btrees of AG 7 to release the unmapped file space.
> - Observe that the the physical updates are resequenced in the correct order
> + Observe that the physical updates are resequenced in the correct order
> when possible.
> Attached to the transaction is a an extent free done (EFD) log item.
> The EFD contains a pointer to the EFI logged in transaction #1 so that log
I feel guilty here. Only considering the diff,
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Not sure if jon pick this or v2, though.
Sorry for inconvenience.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-09-20 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 7:19 [PATCH] Documentation: xfs: Remove repeated word in comments Charles Han
2023-09-18 7:33 ` Bagas Sanjaya
2023-09-19 21:03 ` Dave Chinner
2023-09-19 21:15 ` Matthew Wilcox
2023-09-19 21:55 ` Dave Chinner
2023-09-19 22:09 ` Darrick J. Wong
2023-09-27 12:27 ` Chandan Babu R
2023-09-19 22:10 ` Darrick J. Wong
2023-09-20 0:17 ` Bagas Sanjaya [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=ZQo6G5Z2v1Tk6ShQ@debian.me \
--to=bagasdotme@gmail.com \
--cc=allison.henderson@oracle.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hanchunchao@inspur.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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