FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2024.08.25 onto master branch
Date: Sun, 08 Sep 2024 22:31:54 +0800	[thread overview]
Message-ID: <5129914522d6c2722a877ed68ab65059@kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2663 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.08.25 version.

Thanks,
Zorro

The new head of the master branch is commit:

b14652801e2e generic/615: add to the quick group

New commits:

André Almeida (1):
      [5381898ebaef] common/config: Correctly ignore {TEST|SCRATCH}_DEV for tmpfs

Christoph Hellwig (6):
      [873e36c9c3cc] statx.h: update to latest kernel UAPI
      [0e5f196d0a6a] add a new min_dio_alignment helper
      [4a571eaae784] xfs/424: don't use _min_dio_alignment
      [515e61fdc791] generic: don't use _min_dio_alignment without a device argument
      [ee799a0cf1d4] replace _min_dio_alignment with calls to src/min_dio_alignment
      [b14652801e2e] generic/615: add to the quick group

Darrick J. Wong (1):
      [d77a99817574] xfs: add a test for v1 inodes with nonzero nlink and onlink fields

Filipe Manana (1):
      [e4030c9b6b00] btrfs: test send clones extents with unaligned end offset ending at i_size

Jeff Layton (1):
      [a49385587950] generic/755: test that inode's ctime is updated on unlink

Ma Xinjian (1):
      [1a7f5bbcdd51] xfs/348: add helper tags


Code Diffstat:

 .gitignore              |  1 +
 common/config           |  4 +--
 common/rc               | 15 ----------
 src/Makefile            |  2 +-
 src/min_dio_alignment.c | 66 ++++++++++++++++++++++++++++++++++++++++
 src/statx.h             | 38 +++++++++++++++++++----
 tests/btrfs/319         | 80 +++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/319.out     | 16 ++++++++++
 tests/generic/091       |  2 +-
 tests/generic/095       |  7 +++--
 tests/generic/114       |  2 +-
 tests/generic/240       |  2 +-
 tests/generic/252       |  2 +-
 tests/generic/263       |  2 +-
 tests/generic/329       |  2 +-
 tests/generic/330       |  2 +-
 tests/generic/450       |  2 +-
 tests/generic/465       |  2 +-
 tests/generic/521       |  2 +-
 tests/generic/538       |  2 +-
 tests/generic/551       |  2 +-
 tests/generic/591       |  2 +-
 tests/generic/615       |  2 +-
 tests/generic/617       |  2 +-
 tests/generic/755       | 39 ++++++++++++++++++++++++
 tests/generic/755.out   |  2 ++
 tests/xfs/194           | 11 +++----
 tests/xfs/201           | 47 +++++++++++++++--------------
 tests/xfs/237           |  2 +-
 tests/xfs/239           |  2 +-
 tests/xfs/348           |  7 +++++
 tests/xfs/424           |  2 +-
 tests/xfs/556           |  2 +-
 tests/xfs/608           | 39 ++++++++++++++++++++++++
 tests/xfs/608.out       |  7 +++++
 35 files changed, 345 insertions(+), 74 deletions(-)
--
Zorro Lang
zlang@kernel.org

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

                 reply	other threads:[~2024-09-08 14:31 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=5129914522d6c2722a877ed68ab65059@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