From: cem@kernel.org
To: aalbersh@redhat.com
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: [PATCH v2 0/2] Improve user experience with xfs_fsr
Date: Tue, 17 Mar 2026 17:07:38 +0100 [thread overview]
Message-ID: <20260317160750.186873-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cem@kernel.org>
This is the V2 of this series (my apologies for the delay), based on an
user report via IRC in January.
V2 specific changes are detailed on each patch, but mostly patch 1 was
changed. Patch 2 only the description
Carlos Maiolino (2):
fsr: package function should check for negative errors
fsr: always print error messages from xfrog_defragrange()
fsr/xfs_fsr.c | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-17 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 16:07 cem [this message]
2026-03-17 16:07 ` [PATCH v2 1/2] fsr: package function should check for negative errors cem
2026-03-17 22:12 ` Darrick J. Wong
2026-03-17 16:07 ` [PATCH v2 2/2] fsr: always print error messages from xfrog_defragrange() cem
2026-03-17 22:12 ` Darrick J. Wong
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=20260317160750.186873-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=aalbersh@redhat.com \
--cc=djwong@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