From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: Anand Jain <anand.jain@oracle.com>
Subject: [PATCH 0/9] btrfs-progs: btrfstune: accept multiple devices and cleanup
Date: Wed, 7 Jun 2023 17:59:05 +0800 [thread overview]
Message-ID: <cover.1686131669.git.anand.jain@oracle.com> (raw)
In an attempt to enable btrfstune to accept multiple devices from the
command line, this patch includes some cleanup around the related code
and functions.
Patches 1 to 5 primarily consist of cleanups. Patches 6 and 8 serve as
preparatory changes. Patch 7 enables btrfstune to accept multiple
devices. Patch 9 ensures that btrfstune no longer automatically uses the
system block devices when --noscan option is specified.
Patches 10 and 11 are help and documentation part.
Anand Jain (11):
btrfs-progs: check_mounted_where declare is_btrfs as bool
btrfs-progs: check_mounted_where pack varibles type by size
btrfs-progs: rename struct open_ctree_flags to open_ctree_args
btrfs-progs: optimize device_list_add
btrfs-progs: simplify btrfs_scan_one_device()
btrfs-progs: factor out btrfs_scan_stdin_devices
btrfs-progs: tune: add stdin device list
btrfs-progs: refactor check_where_mounted with noscan option
btrfs-progs: tune: add noscan option
btrfs-progs: tune: add help for multiple devices and noscan option
btrfs-progs: Documentation: update btrfstune --noscan option
Documentation/btrfstune.rst | 4 ++++
btrfs-find-root.c | 2 +-
check/main.c | 2 +-
cmds/filesystem.c | 2 +-
cmds/inspect-dump-tree.c | 39 ++++---------------------------------
cmds/rescue.c | 4 ++--
cmds/restore.c | 2 +-
common/device-scan.c | 39 +++++++++++++++++++++++++++++++++++++
common/device-scan.h | 1 +
common/open-utils.c | 21 +++++++++++---------
common/open-utils.h | 3 ++-
common/utils.c | 3 ++-
image/main.c | 4 ++--
kernel-shared/disk-io.c | 8 ++++----
kernel-shared/disk-io.h | 4 ++--
kernel-shared/volumes.c | 14 +++++--------
mkfs/main.c | 2 +-
tune/main.c | 25 +++++++++++++++++++-----
18 files changed, 104 insertions(+), 75 deletions(-)
--
2.31.1
next reply other threads:[~2023-06-07 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 9:59 Anand Jain [this message]
2023-06-07 9:59 ` [PATCH 01/11] btrfs-progs: check_mounted_where declare is_btrfs as bool Anand Jain
2023-06-07 9:59 ` [PATCH 02/11] btrfs-progs: check_mounted_where pack varibles type by size Anand Jain
2023-06-07 9:59 ` [PATCH 03/11] btrfs-progs: rename struct open_ctree_flags to open_ctree_args Anand Jain
2023-06-07 9:59 ` [PATCH 04/11] btrfs-progs: optimize device_list_add Anand Jain
2023-06-07 9:59 ` [PATCH 05/11] btrfs-progs: simplify btrfs_scan_one_device() Anand Jain
2023-06-07 9:59 ` [PATCH 06/11] btrfs-progs: factor out btrfs_scan_stdin_devices Anand Jain
2023-06-07 9:59 ` [PATCH 07/11] btrfs-progs: tune: add stdin device list Anand Jain
2023-06-07 9:59 ` [PATCH 08/11] btrfs-progs: refactor check_where_mounted with noscan option Anand Jain
2023-06-07 9:59 ` [PATCH 09/11] btrfs-progs: tune: add " Anand Jain
2023-06-07 9:59 ` [PATCH 10/11] btrfs-progs: tune: add help for multiple devices and " Anand Jain
2023-06-07 9:59 ` [PATCH 11/11] btrfs-progs: Documentation: update btrfstune --noscan option Anand Jain
2023-06-07 10:43 ` [PATCH 0/9] btrfs-progs: btrfstune: accept multiple devices and cleanup Anand Jain
2023-06-07 11:06 ` Qu Wenruo
2023-06-08 0:20 ` Anand Jain
2023-06-08 1:42 ` Qu Wenruo
2023-06-08 4:26 ` Anand Jain
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.1686131669.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).