From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com, zlang@redhat.com
Cc: Catherine Hoang <catherine.hoang@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET 0/2] fstests: random fixes
Date: Tue, 19 Apr 2022 10:31:54 -0700 [thread overview]
Message-ID: <165038951495.1677615.10687913612774985228.stgit@magnolia> (raw)
Hi all,
Here's the usual batch of odd fixes for fstests.
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=random-fixes
xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=random-fixes
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=random-fixes
---
tests/generic/019 | 4 ++--
tests/xfs/019 | 3 +--
tests/xfs/019.out | 2 +-
3 files changed, 4 insertions(+), 5 deletions(-)
next reply other threads:[~2022-04-19 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:31 Darrick J. Wong [this message]
2022-04-19 17:32 ` [PATCH 1/2] xfs/019: fix golden output for files created in setgid dir Darrick J. Wong
2022-04-19 18:33 ` Zorro Lang
2022-04-19 18:38 ` Darrick J. Wong
2022-04-20 14:47 ` Zorro Lang
2022-04-20 16:03 ` Catherine Hoang
2022-04-19 17:32 ` [PATCH 2/2] generic/019: fix incorrect unset statements Darrick J. Wong
2022-04-19 18:34 ` Zorro Lang
-- strict thread matches above, loose matches on Subject: below --
2022-04-11 22:54 [PATCHSET 0/2] fstests: random fixes Darrick J. Wong
2021-09-01 0:11 Darrick J. Wong
2021-08-17 23:52 Darrick J. Wong
2021-04-21 0:22 Darrick J. Wong
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=165038951495.1677615.10687913612774985228.stgit@magnolia \
--to=djwong@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).