All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2024.05.26 onto master branch
Date: Sun, 09 Jun 2024 22:41:34 +0800	[thread overview]
Message-ID: <2416f53ef09e6ec083b540bc7aa4e33f@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2806 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 v2024.05.26 version.

Thanks,
Zorro

The new head of the master branch is commit:

e46fa3a7dae4 Remove richacl support

New commits:

Anand Jain (1):
      [692bef09cfad] btrfs/741: add commit ID in _fixed_by_kernel_commit

Carlos Maiolino (1):
      [e099ba0087d8] check: log kernel version in check.log

Chandan Babu R (1):
      [86e123019c81] _test_mkfs: Include external log device (if any) when creating fs on TEST_DEV

Chen Hanxiao (1):
      [be5ec474127b] generic/742: require FIEMAP support

David Sterba (1):
      [e46fa3a7dae4] Remove richacl support

Filipe Manana (1):
      [26d69e8df390] generic/733: add commit ID for btrfs

Josef Bacik (5):
      [e0aca4b09d81] generic/352: require no compression
      [c99901745c41] generic/027: require no compression
      [a0e33b4b4731] generic/269: require no compression
      [73f45a1ff44e] btrfs/{140,141}: verify read-repair test data by md5sum
      [a42f8a6be29e] fstests: mkfs the scratch device if we have missing profiles

Qu Wenruo (1):
      [fa81eef946b9] fstests: btrfs/301: handle auto-removed qgroups


Code Diffstat:

 check                 |   1 +
 common/config         |   2 -
 common/ext4           |   9 ----
 common/rc             |  55 +-------------------
 doc/group-names.txt   |   1 -
 tests/btrfs/011       |   6 +++
 tests/btrfs/140       |  15 +++++-
 tests/btrfs/140.out   |  34 ------------
 tests/btrfs/141       |  16 +++++-
 tests/btrfs/141.out   |  34 ------------
 tests/btrfs/301       |  14 +++--
 tests/generic/027     |   4 ++
 tests/generic/269     |   2 +-
 tests/generic/352     |   4 ++
 tests/generic/362     |  93 ---------------------------------
 tests/generic/362.out |  94 ----------------------------------
 tests/generic/363     |  86 -------------------------------
 tests/generic/363.out | 139 --------------------------------------------------
 tests/generic/364     |  67 ------------------------
 tests/generic/364.out |  39 --------------
 tests/generic/365     |  61 ----------------------
 tests/generic/365.out |   9 ----
 tests/generic/366     |  54 --------------------
 tests/generic/366.out |  11 ----
 tests/generic/367     |  53 -------------------
 tests/generic/367.out |  11 ----
 tests/generic/368     |  53 -------------------
 tests/generic/368.out |   7 ---
 tests/generic/369     |  94 ----------------------------------
 tests/generic/369.out |  24 ---------
 tests/generic/370     |  58 ---------------------
 tests/generic/370.out |  19 -------
 tests/generic/733     |  15 ++++--
 tests/generic/741     |   2 +-
 tests/generic/742     |   1 +
 35 files changed, 72 insertions(+), 1115 deletions(-)
--
Zorro Lang
zlang@kernel.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2024-06-09 14:41 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=2416f53ef09e6ec083b540bc7aa4e33f@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 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.