From: Eric Sandeen <sandeen@redhat.com>
To: Xin Gao <gaoxin@cdjrlc.com>, djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Fix comment typo
Date: Fri, 22 Jul 2022 15:20:32 -0500 [thread overview]
Message-ID: <c0cc00bd-9904-9ede-26b2-66737acffaf2@redhat.com> (raw)
In-Reply-To: <20220722194328.18365-1-gaoxin@cdjrlc.com>
On 7/22/22 2:43 PM, Xin Gao wrote:
> The double `that' is duplicated in line 575, remove one.
>
> Signed-off-by: Xin Gao <gaoxin@cdjrlc.com>
> ---
> fs/xfs/xfs_trans.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
> index 82cf0189c0db..d055b0938eb9 100644
> --- a/fs/xfs/xfs_trans.c
> +++ b/fs/xfs/xfs_trans.c
> @@ -572,7 +572,7 @@ xfs_trans_apply_sb_deltas(
> * xfs_trans_unreserve_and_mod_sb() is called to release unused reservations and
> * apply superblock counter changes to the in-core superblock. The
> * t_res_fdblocks_delta and t_res_frextents_delta fields are explicitly NOT
> - * applied to the in-core superblock. The idea is that that has already been
> + * applied to the in-core superblock. The idea is that has already been
> * done.
> *
> * If we are not logging superblock counters, then the inode allocated/free and
NAK
The comment is correct
next prev parent reply other threads:[~2022-07-22 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 19:43 [PATCH] xfs: Fix comment typo Xin Gao
2022-07-22 20:20 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 19:40 Xin Gao
2022-07-22 19:36 Xin Gao
2022-07-22 20:20 ` Eric Sandeen
2022-07-22 19:32 Xin Gao
2022-07-22 2:26 Xin Gao
2022-07-22 2:46 ` Darrick J. Wong
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=c0cc00bd-9904-9ede-26b2-66737acffaf2@redhat.com \
--to=sandeen@redhat.com \
--cc=djwong@kernel.org \
--cc=gaoxin@cdjrlc.com \
--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