From: Chandan Babu R <chandanbabu@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [GIT PULL] xfs: use busy extents for fstrim
Date: Wed, 04 Oct 2023 10:33:22 +0530 [thread overview]
Message-ID: <87o7hfq8m1.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <ZRygqkCkbH32I+x9@dread.disaster.area>
On Wed, Oct 04, 2023 at 10:15:54 AM +1100, Dave Chinner wrote:
> Hi Chandan,
>
> Can you please pull the changes to fstrim behaviour from the signed
> tag below? This has been rebased on 6.6-rc4 so should merge cleanly
> into a current tree.
>
Thank you. I have merged the changes and started an fstests run now. I will
push the changes to xfs-linux's for-next branch tomorrow if I do not encounter
any regressions.
--
Chandan
prev parent reply other threads:[~2023-10-04 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 23:15 [GIT PULL] xfs: use busy extents for fstrim Dave Chinner
2023-10-04 5:03 ` Chandan Babu R [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=87o7hfq8m1.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=david@fromorbit.com \
--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