From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 0/5] Misceillaneous ext4 test fix ups
Date: Fri, 24 Jun 2022 23:07:13 -0400 [thread overview]
Message-ID: <20220625030718.1215980-1-tytso@mit.edu> (raw)
The first patch has been in my tree for a long time, but I had forgotten
to send it upstream.
The last two patches are a rewrite (in response to comments) of
"ext4/054,ext4/055: don't run when using DAX" which I had sent in late
April.
Theodore Ts'o (5):
ext4/050: support indirect as well as extent mapped journals
ext4/044: skip test if the file system does not have a journal
ext4/045: clean up unnecessary arguments to _require_e2fsprogs
ext4/054: skip test if the dax mount option is enabled
ext4/055: skip test if dax mount option is used
common/rc | 3 +++
tests/ext4/044 | 6 ++++++
tests/ext4/045 | 2 +-
tests/ext4/050 | 58 +++++---------------------------------------------
tests/ext4/054 | 5 ++---
tests/ext4/055 | 1 +
6 files changed, 18 insertions(+), 57 deletions(-)
--
2.31.0
next reply other threads:[~2022-06-25 3:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 3:07 Theodore Ts'o [this message]
2022-06-25 3:07 ` [PATCH 1/5] ext4/050: support indirect as well as extent mapped journals Theodore Ts'o
2022-06-28 4:24 ` Zorro Lang
2022-06-25 3:07 ` [PATCH 2/5] ext4/044: skip test if the file system does not have a journal Theodore Ts'o
2022-06-28 4:28 ` Zorro Lang
2022-06-28 4:32 ` Zorro Lang
2022-06-28 18:20 ` Theodore Ts'o
2022-06-25 3:07 ` [PATCH 3/5] ext4/045: clean up unnecessary arguments to _require_e2fsprogs Theodore Ts'o
2022-06-28 4:37 ` Zorro Lang
2022-06-28 18:21 ` Theodore Ts'o
2022-06-25 3:07 ` [PATCH 4/5] ext4/054: skip test if the dax mount option is enabled Theodore Ts'o
2022-06-28 4:39 ` Zorro Lang
2022-06-25 3:07 ` [PATCH 5/5] ext4/055: skip test if dax mount option is used Theodore Ts'o
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=20220625030718.1215980-1-tytso@mit.edu \
--to=tytso@mit.edu \
--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