From: "Darrick J. Wong" <djwong@kernel.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org
Subject: Re: [PATCH] xfs: Rudimentary typo fixes
Date: Sat, 20 Mar 2021 13:17:54 -0700 [thread overview]
Message-ID: <20210320201754.GZ22100@magnolia> (raw)
In-Reply-To: <20210320195626.19400-1-unixbhaskar@gmail.com>
On Sun, Mar 21, 2021 at 01:26:26AM +0530, Bhaskar Chowdhury wrote:
>
> s/filesytem/filesystem/
> s/instrumention/instrumentation/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Looks good to me,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_log_recover.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index 97f31308de03..ffa4f6f2f31e 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -2736,7 +2736,7 @@ xlog_recover_process_one_iunlink(
> * of log space.
> *
> * This behaviour is bad for latency on single CPU and non-preemptible kernels,
> - * and can prevent other filesytem work (such as CIL pushes) from running. This
> + * and can prevent other filesystem work (such as CIL pushes) from running. This
> * can lead to deadlocks if the recovery process runs out of log reservation
> * space. Hence we need to yield the CPU when there is other kernel work
> * scheduled on this CPU to ensure other scheduled work can run without undue
> @@ -3404,7 +3404,7 @@ xlog_recover(
>
> /*
> * Delay log recovery if the debug hook is set. This is debug
> - * instrumention to coordinate simulation of I/O failures with
> + * instrumentation to coordinate simulation of I/O failures with
> * log recovery.
> */
> if (xfs_globals.log_recovery_delay) {
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-03-20 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 19:56 [PATCH] xfs: Rudimentary typo fixes Bhaskar Chowdhury
2021-03-20 20:17 ` Darrick J. Wong [this message]
2021-03-20 22:34 ` 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=20210320201754.GZ22100@magnolia \
--to=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
/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