From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 47a1238bdb23
Date: Sun, 10 Oct 2021 23:28:23 +0800 [thread overview]
Message-ID: <6163069b.1c69fb81.bc811.b886@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1698 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 is a bugfix only update and should not introduce
new failures.
Thanks,
Eryu
The new head of the master branch is commit:
47a1238bdb23 common/log: fix *_dump_log routines for ext4
New commits:
Catherine Hoang (4):
[69575301c85e] fstests: rename _scratch_inject_logprint to _scratch_remount_dump_log
[d888261aa0e6] fstests: rename _test_inject_logprint to _test_remount_dump_log
[e61c2b753cc4] common/log: move *_dump_log routines to common/log
[47a1238bdb23] common/log: fix *_dump_log routines for ext4
Luis Henriques (2):
[7a2cdfa745aa] common/rc: add _require_user_exists() to check if a user exists
[dfae4068a824] generic/079: make sure users 'nobody' and 'daemon' exist
Yang Xu (1):
[aca74d17ccfa] xfs/540: use _scratch_xfs_set_metadata_field api
Code Diffstat:
common/inject | 26 --------------------------
common/log | 30 ++++++++++++++++++++++++++++--
common/rc | 27 ++++++++++++++++++---------
tests/generic/079 | 2 ++
tests/xfs/312 | 2 +-
tests/xfs/313 | 2 +-
tests/xfs/314 | 2 +-
tests/xfs/315 | 2 +-
tests/xfs/316 | 2 +-
tests/xfs/317 | 2 +-
tests/xfs/318 | 2 +-
tests/xfs/319 | 2 +-
tests/xfs/320 | 2 +-
tests/xfs/321 | 2 +-
tests/xfs/322 | 2 +-
tests/xfs/323 | 2 +-
tests/xfs/324 | 2 +-
tests/xfs/325 | 2 +-
tests/xfs/326 | 2 +-
tests/xfs/329 | 2 +-
tests/xfs/540 | 10 +++++-----
21 files changed, 69 insertions(+), 58 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-10-10 15:28 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=6163069b.1c69fb81.bc811.b886@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