All of lore.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: aalbersh@redhat.com
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: [PATCH v4 0/2] Improve user experience with xfs_fsr
Date: Tue,  7 Apr 2026 13:14:58 +0200	[thread overview]
Message-ID: <20260407111507.79977-1-cem@kernel.org> (raw)

From: Carlos Maiolino <cem@kernel.org>

This is the V4 of this series,
this fixes an issue based on an user report via IRC in January.

The only change in this series in in patch 2 which adds back the
fprintf() call I accidentally removed while rebasing it.


Carlos Maiolino (2):
  fsr: package function should check for negative errors
  fsr: always print error messages from xfrog_defragrange()

 fsr/xfs_fsr.c | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

-- 
2.53.0

             reply	other threads:[~2026-04-07 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 11:14 cem [this message]
2026-04-07 11:14 ` [PATCH v4 1/2] fsr: package function should check for negative errors cem
2026-04-07 11:15 ` [PATCH v4 2/2] fsr: always print error messages from xfrog_defragrange() cem
2026-04-07 15:07   ` 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=20260407111507.79977-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 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.