From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: Zorro Lang <zlang@redhat.com>, fstests@vger.kernel.org
Cc: djwong@kernel.org, fdmanana@suse.com, ritesh.list@gmail.com,
naohiro.aota@wdc.com, wqu@suse.com
Subject: [PATCH v2 0/6] Atomic write test fixes & refactoring
Date: Fri, 10 Apr 2026 12:06:00 +0530 [thread overview]
Message-ID: <cover.1775802601.git.ojaswin@linux.ibm.com> (raw)
* Changes since v1 [1] *
* Add a helper to correctly get sysfs queue path, and
use it treewide for consistent handling.
* Collect RVB from Darrick on patch 1
* generic/765: Detect if mkfs succeeds
* generic/775: Make variable local and rename it for clarity
For treewide changes I've tried to CC respective maintainers and
original authors. Please let me know if someone else needs to be looped
in.
[1] https://lore.kernel.org/fstests/726e43008315a1bed018c1b43aae2458aebc03bc.1775039135.git.ojaswin@linux.ibm.com/
Ojaswin Mujoo (6):
ext4/061,062: Minor fixes and refactoring
common/rc: Add _sysfs_queue_path helper with partition support
generic/765: Fix sysfs queue path for nvme partitions
generic/765: Ignore mkfs warning
generic/775: Fix an infinite loop due to variable name clash
treewide: Use _sysfs_queue_path helper in all queue access locations
common/encrypt | 7 ++-----
common/rc | 36 ++++++++++++++++++++++++++++++++----
common/report | 20 +++++++++++---------
common/zoned | 5 +++--
tests/btrfs/076 | 11 +++++++----
tests/btrfs/237 | 5 +++--
tests/btrfs/273 | 4 +++-
tests/btrfs/283 | 4 +++-
tests/ext4/061 | 28 ++++++++++++++++++++--------
tests/ext4/062 | 26 +++++++++++++++++++-------
tests/generic/765 | 12 +++++++-----
tests/generic/775 | 3 ++-
12 files changed, 112 insertions(+), 49 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-10 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 6:36 Ojaswin Mujoo [this message]
2026-04-10 6:36 ` [PATCH 1/6] ext4/061,062: Minor fixes and refactoring Ojaswin Mujoo
2026-04-10 6:36 ` [PATCH 2/6] common/rc: Add _sysfs_queue_path helper with partition support Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 3/6] generic/765: Fix sysfs queue path for nvme partitions Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 4/6] generic/765: Ignore mkfs warning Ojaswin Mujoo
2026-04-10 16:54 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 5/6] generic/775: Fix an infinite loop due to variable name clash Ojaswin Mujoo
2026-04-10 16:51 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 6/6] treewide: Use _sysfs_queue_path helper in all queue access locations Ojaswin Mujoo
2026-04-10 16:52 ` 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=cover.1775802601.git.ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=ritesh.list@gmail.com \
--cc=wqu@suse.com \
--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