From: Christoph Hellwig <hch@lst.de>
To: zlang@redhat.com
Cc: djwong@kernel.org, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: _supports_xfs_scrub cleanups v2
Date: Fri, 12 Jan 2024 06:08:29 +0100 [thread overview]
Message-ID: <20240112050833.2255899-1-hch@lst.de> (raw)
Hi all,
this series adds a missing scrub support fix to xfs/262 and cleans
up a few bits around this.
Changes since v1:
- use _fail
- also annotate xfs/506
next reply other threads:[~2024-01-12 5:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 5:08 Christoph Hellwig [this message]
2024-01-12 5:08 ` [PATCH 1/4] xfs: check that the mountpoint is actually mounted in _supports_xfs_scrub Christoph Hellwig
2024-01-12 13:20 ` Zorro Lang
2024-01-12 16:41 ` Darrick J. Wong
2024-01-12 5:08 ` [PATCH 2/4] xfs: add a _scratch_require_xfs_scrub helper Christoph Hellwig
2024-01-12 13:32 ` Zorro Lang
2024-01-12 14:14 ` Christoph Hellwig
2024-01-12 16:42 ` Darrick J. Wong
2024-01-12 5:08 ` [PATCH 3/4] xfs/262: call _scratch_require_xfs_scrub Christoph Hellwig
2024-01-12 16:43 ` Darrick J. Wong
2024-01-12 5:08 ` [PATCH 4/4] xfs/506: " Christoph Hellwig
2024-01-12 16:43 ` 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=20240112050833.2255899-1-hch@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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