Linux XFS filesystem development
 help / color / mirror / Atom feed
From: caina <caina@uniontech.com>
To: cem@kernel.org
Cc: djwong@kernel.org, linux-xfs@vger.kernel.org, hch@infradead.org,
	linux-kernel@vger.kernel.org, kernel@uniontech.com
Subject: Re: [PATCH v3] xfs: clean up spelling and grammar errors in comments
Date: Wed, 15 Jul 2026 14:34:32 +0800	[thread overview]
Message-ID: <20260715063432.26491-1-caina@uniontech.com> (raw)
In-Reply-To: <alO0W1-tul6jgB3l@nidhogg.toxiclabs.cc>

On Fri, Jul 03, 2026 at 05:34:02PM +0800, caina wrote:
> This patch does not apply on top of for-next, please rebase it on top of
> for-next and re-send.

> Also don't forget to Cc me to the patch.

Hi Carlos Maiolino,

Thank you for the reminder. I have rebased the patch onto the latest
for-next branch and sent out v4.

Thanks,
Caina

      reply	other threads:[~2026-07-15  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  9:34 [PATCH v3] xfs: clean up spelling and grammar errors in comments caina
2026-07-06  6:03 ` Christoph Hellwig
2026-07-12 15:37 ` Carlos Maiolino
2026-07-15  6:34   ` 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=20260715063432.26491-1-caina@uniontech.com \
    --to=caina@uniontech.com \
    --cc=cem@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox