From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2022.05.29 onto master branch
Date: Sun, 05 Jun 2022 17:55:40 +0800 [thread overview]
Message-ID: <20220605095543.3BE24C385A5@smtp.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3059 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
has just been updated to v2022.05.29 version (merged from for-next).
Thanks,
Zorro
The new head of the master branch is commit:
d3cc66012a28 btrfs: test direct I/O read repair with interleaved corrupted sectors
New commits:
Amir Goldstein (1):
[4fb72cffd9e3] xfs: annotate fix commits for upcoming 5.10.y backports
Christoph Hellwig (10):
[68da7b2ab804] btrfs: add a helpers for read repair testing
[b6daf3447d4d] btrfs/140: use common read repair helpers
[bd9306394f2c] btrfs/141: use common read repair helpers
[0baec6a82ada] btrfs/142: use common read repair helpers
[9106f321f91a] btrfs/143: use common read repair helpers
[ebb554efcbf7] btrfs/157: use _btrfs_get_first_logical
[cd87ca221a32] btrfs/215: use _btrfs_get_first_logical
[94b0abc48f77] btrfs: test repair with sectors corrupted in multiple mirrors
[fa1bcba58824] btrfs: test buffered I/O read repair with interleaved corrupted sectors
[d3cc66012a28] btrfs: test direct I/O read repair with interleaved corrupted sectors
Darrick J. Wong (1):
[a8812199578b] xfs/545: check for fallocate support before running test
Luís Henriques (2):
[96ca82d8e5d8] ceph/002: fix test expected output
[e57024a30588] ceph/001: skip metrics check if no copyfrom mount option is used
Zorro Lang (2):
[61775fb9e1ab] common: source base fs specific common file
[7eb01db2b776] tests: remove redundant common/$FSTYP importing
Code Diffstat:
common/btrfs | 75 ++++++++++++++++++++++++++++++++++++
common/config | 60 +++++++++++++++++++++++++++++
common/overlay | 4 ++
common/rc | 49 +----------------------
tests/btrfs/140 | 13 +------
tests/btrfs/141 | 15 +-------
tests/btrfs/142 | 10 ++---
tests/btrfs/143 | 10 ++---
tests/btrfs/157 | 2 +-
tests/btrfs/177 | 1 -
tests/btrfs/215 | 2 +-
tests/btrfs/258 | 1 -
tests/btrfs/259 | 1 -
tests/btrfs/265 | 85 ++++++++++++++++++++++++++++++++++++++++
tests/btrfs/265.out | 75 ++++++++++++++++++++++++++++++++++++
tests/btrfs/266 | 93 ++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/266.out | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/267 | 93 ++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/267.out | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/ceph/001 | 6 ++-
tests/ceph/002.out | 2 +-
tests/generic/623 | 3 ++
tests/generic/631 | 2 +
tests/generic/646 | 3 ++
tests/generic/649 | 3 ++
tests/xfs/145 | 3 ++
tests/xfs/177 | 2 +
tests/xfs/422 | 1 -
tests/xfs/423 | 1 -
tests/xfs/513 | 3 ++
tests/xfs/517 | 1 -
tests/xfs/539 | 7 +++-
tests/xfs/542 | 3 ++
tests/xfs/545 | 1 +
34 files changed, 750 insertions(+), 98 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-06-05 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220605095543.3BE24C385A5@smtp.kernel.org \
--to=zlang@kernel.org \
--cc=fstests@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