Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Xin Gao <gaoxin@cdjrlc.com>
To: djwong@kernel.org
Cc: dchinner@redhat.com, chandan.babu@oracle.com,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Xin Gao <gaoxin@cdjrlc.com>
Subject: [PATCH] xfs: Fix comment typo
Date: Sat, 23 Jul 2022 03:40:14 +0800	[thread overview]
Message-ID: <20220722194014.18184-1-gaoxin@cdjrlc.com> (raw)

The double `extent' is duplicated in line 837, remove one.

Signed-off-by: Xin Gao <gaoxin@cdjrlc.com>
---
 fs/xfs/libxfs/xfs_alloc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
index d3f2886fdc08..f6bd9181cb13 100644
--- a/fs/xfs/libxfs/xfs_alloc.c
+++ b/fs/xfs/libxfs/xfs_alloc.c
@@ -833,7 +833,7 @@ xfs_alloc_cur_close(
 /*
  * Check an extent for allocation and track the best available candidate in the
  * allocation structure. The cursor is deactivated if it has entered an out of
- * range state based on allocation arguments. Optionally return the extent
+ * range state based on allocation arguments. Optionally return the
  * extent geometry and allocation status if requested by the caller.
  */
 static int
-- 
2.30.2


             reply	other threads:[~2022-07-22 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 19:40 Xin Gao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-22 19:43 [PATCH] xfs: Fix comment typo Xin Gao
2022-07-22 20:20 ` Eric Sandeen
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=20220722194014.18184-1-gaoxin@cdjrlc.com \
    --to=gaoxin@cdjrlc.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@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