From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 968c531cbe58
Date: Mon, 15 Jul 2019 01:59:55 +0800 [thread overview]
Message-ID: <5d2b6da2.1c69fb81.dacaf.3941@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
have just been updated. This update contains various fixes and there should be
no new failures after this update. Note that kernel version is also printed
along with kernel release in the check output header.
Thanks,
Eryu
The new head of the master branch is commit:
968c531cbe58 xfs/119: fix MKFS_OPTIONS exporting
New commits:
Darrick J. Wong (3):
[241c25a975f4] xfs: rework min log size helper
[ee3677a86820] xfs/016: calculate minimum log size and end locations
[968c531cbe58] xfs/119: fix MKFS_OPTIONS exporting
Eric Biggers (1):
[856f357c6a5c] generic/399: don't rely on xfs_io exit status
Filipe Manana (1):
[55cc523b0ec4] btrfs/189: make the test work on systems with a page size greater than 4Kb
Mauricio Faria de Oliveira (1):
[a4c1696f8c4b] common/rc: print out kernel version too
Yang Xu (1):
[f036a4da857c] generic/553[4]: correct kernel fix commit
Zorro Lang (1):
[7ef6a36702b2] xfs/449: test xfs_info on a mounted block device
Code Diffstat:
common/rc | 2 +-
common/xfs | 25 ++++++++++++++++++--
tests/btrfs/189 | 10 ++++----
tests/btrfs/189.out | 4 ++--
tests/generic/399 | 46 ++++++++++++++++++++++---------------
tests/generic/553 | 2 +-
tests/generic/554 | 2 +-
tests/xfs/016 | 66 ++++++++++++++++++++++++++++++++++++++++++-----------
tests/xfs/016.out | 1 +
tests/xfs/119 | 3 ++-
tests/xfs/449 | 13 +++++++----
11 files changed, 127 insertions(+), 47 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2019-07-14 18:00 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=5d2b6da2.1c69fb81.dacaf.3941@mx.google.com \
--to=guaneryu@gmail.com \
--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