From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrew Kreimer <algonell@gmail.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] xfs: fix a typo
Date: Wed, 2 Oct 2024 14:28:00 -0700 [thread overview]
Message-ID: <20241002212800.GF21853@frogsfrogsfrogs> (raw)
In-Reply-To: <20241002211948.10919-1-algonell@gmail.com>
On Thu, Oct 03, 2024 at 12:19:48AM +0300, Andrew Kreimer wrote:
> Fix a typo in comments.
>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
Looks good,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_log_recover.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index ec766b4bc853..a13bf53fea49 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -1849,7 +1849,7 @@ xlog_find_item_ops(
> * from the transaction. However, we can't do that until after we've
> * replayed all the other items because they may be dependent on the
> * cancelled buffer and replaying the cancelled buffer can remove it
> - * form the cancelled buffer table. Hence they have tobe done last.
> + * form the cancelled buffer table. Hence they have to be done last.
> *
> * 3. Inode allocation buffers must be replayed before inode items that
> * read the buffer and replay changes into it. For filesystems using the
> --
> 2.39.5
>
>
next prev parent reply other threads:[~2024-10-02 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:19 [PATCH] xfs: fix a typo Andrew Kreimer
2024-10-02 21:28 ` Darrick J. Wong [this message]
2024-10-03 5:59 ` Dan Carpenter
2024-10-03 8:30 ` Andrew Kreimer
-- strict thread matches above, loose matches on Subject: below --
2021-03-22 6:39 [PATCH] xfs: Fix " Bhaskar Chowdhury
2021-03-22 10:29 ` Pavel Reichl
2021-03-22 18:48 ` Randy Dunlap
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=20241002212800.GF21853@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=algonell@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=kernel-janitors@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).