linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Xichao Zhao <zhao.xichao@vivo.com>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xfs: fix "acheive"->"achieve"
Date: Fri, 8 Aug 2025 07:52:48 -0700	[thread overview]
Message-ID: <20250808145248.GU2672049@frogsfrogsfrogs> (raw)
In-Reply-To: <20250808084321.230969-1-zhao.xichao@vivo.com>

On Fri, Aug 08, 2025 at 04:43:21PM +0800, Xichao Zhao wrote:
> Trivial fix to spelling mistake in comment text.

Already submitted to the list[1], please read the archives before you
hit send.

[1] https://lore.kernel.org/linux-xfs/jjpiu6ot5kndjcggvoochddt7qq6vxmijdlog2vcp7y6pldhy3@wmbpth6y5af4/T/#u

--D

> 
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
> ---
>  fs/xfs/xfs_inode.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 9c39251961a3..4c66bbe23001 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -1745,7 +1745,7 @@ xfs_ifree_cluster(
>  		 * IO and it won't be unlocked until the cluster freeing has
>  		 * been committed to the journal and the buffer unpinned. If it
>  		 * is written, we want to know about it, and we want it to
> -		 * fail. We can acheive this by adding a write verifier to the
> +		 * fail. We can achieve this by adding a write verifier to the
>  		 * buffer.
>  		 */
>  		bp->b_flags |= XBF_DONE;
> -- 
> 2.34.1
> 
> 

      reply	other threads:[~2025-08-08 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  8:43 [PATCH v2] xfs: fix "acheive"->"achieve" Xichao Zhao
2025-08-08 14:52 ` Darrick J. Wong [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=20250808145248.GU2672049@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zhao.xichao@vivo.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;
as well as URLs for NNTP newsgroup(s).