All of lore.kernel.org
 help / color / mirror / Atom feed
From: caina <caina@uniontech.com>
To: hch@infradead.org
Cc: djwong@kernel.org, linux-xfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@uniontech.com
Subject: Re: [PATCH v2] xfs: clean up spelling and grammar errors in comments
Date: Fri,  3 Jul 2026 17:23:21 +0800	[thread overview]
Message-ID: <20260703092321.1509-1-caina@uniontech.com> (raw)
In-Reply-To: <ajve0YCxD_u62phh@infradead.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=yes, Size: 601 bytes --]

On Wed, Jun 24, 2026 at 06:42:41AM -0700, Christoph Hellwig wrote:
> On Wed, Jun 17, 2026 at 01:50:52PM +0800, caina wrote:
> >  /*
> >   * Set up an in-memory buffer cache so that we can use the xfbtree.  Allocating
> > - * a shmem file might take loks, so we cannot be in transaction context.  Park
> > + * a shmem file might take looks, so we cannot be in transaction context.  Park
> 
> I think this should be locks, not looks.

Hi Christoph,

Thank you for catching this. You're absolutely right – it should be
"locks" (as in "taking locks"), not "looks". I will fix this in v3.

Thanks,
Caina

      parent reply	other threads:[~2026-07-03  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  2:09 [PATCH] xfs: clean up spelling and grammar errors in comments caina
2026-06-16 13:08 ` Christoph Hellwig
2026-06-17  5:26   ` caina
2026-06-17  5:50 ` [PATCH v2] " caina
2026-06-24 13:42   ` Christoph Hellwig
2026-06-24 17:37     ` Darrick J. Wong
2026-07-03  9:23     ` caina [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=20260703092321.1509-1-caina@uniontech.com \
    --to=caina@uniontech.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=kernel@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.