From: Christoph Hellwig <hch@lst.de>
To: daejun7.park@samsung.com
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dgc@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: don't skip free extents in later batches of a whole-AG FITRIM
Date: Wed, 28 Oct 2026 16:03:53 +0100 [thread overview]
Message-ID: <20261028150353.GA16152@lst.de> (raw)
In-Reply-To: <20261026-xfs-fitrim-skip-v1-1-cddd8414f99c@samsung.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-10-28 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 1:54 [PATCH 0/2] xfs: discard every free extent in a whole-AG FITRIM Daejun Park via B4 Relay
2026-10-26 1:54 ` [PATCH 1/2] xfs: don't skip free extents in later batches of " Daejun Park via B4 Relay
2026-10-28 15:03 ` Christoph Hellwig [this message]
2026-10-26 1:54 ` [PATCH 2/2] xfs: don't skip free extents of the longest length in " Daejun Park via B4 Relay
2026-10-28 15:04 ` Christoph Hellwig
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=20261028150353.GA16152@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@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