All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6 v3] btrfs-progs: cleanup and preparatory around device scan
Date: Tue, 13 Jun 2023 18:26:51 +0800	[thread overview]
Message-ID: <cover.1686484067.git.anand.jain@oracle.com> (raw)

v3: Contains fixes as per review comments; details are in the individual
    patches.

    Patches dropped:
      btrfs-progs: check_mounted_where: pack varibles type by size
      btrfs-progs: btrfs_scan_one_device: drop local variable ret
    Patch added:
      btrfs-progs: drop open_ctree_flags in cmd_inspect_dump_tree

v2: I have separated preparatory and cleanups from the introduction of new
    features so that they can be easily modified with a smaller set of patches.

    Added missing git changelogs. (Looks like sshfs lost my last few changes,
    now fixed).

--- original cover page ---
In an attempt to enable btrfstune to accept multiple devices from the
command line, this patch includes some cleanup around the related
preparatory work around the device scan code.

Patches 1 to 5 primarily consist of cleanups. Patches 6 and 7 serve as
preparatory changes.

Anand Jain (6):
  btrfs-progs: check_mounted_where: declare is_btrfs as bool
  btrfs-progs: rename struct open_ctree_flags to open_ctree_args
  btrfs-progs: drop open_ctree_flags in cmd_inspect_dump_tree
  btrfs-progs: device_list_add: optimize arguments drop devid
  btrfs-progs: factor out btrfs_scan_argv_devices
  btrfs-progs: refactor check_where_mounted with noscan argument

 btrfs-find-root.c        |  8 +++---
 check/main.c             | 14 +++++-----
 cmds/filesystem.c        |  8 +++---
 cmds/inspect-dump-tree.c | 55 ++++++++--------------------------------
 cmds/rescue.c            | 16 ++++++------
 cmds/restore.c           | 12 ++++-----
 common/device-scan.c     | 40 +++++++++++++++++++++++++++++
 common/device-scan.h     |  1 +
 common/open-utils.c      | 11 +++++---
 common/open-utils.h      |  3 ++-
 common/utils.c           |  3 ++-
 image/main.c             | 16 ++++++------
 kernel-shared/disk-io.c  | 50 ++++++++++++++++++------------------
 kernel-shared/disk-io.h  |  4 +--
 kernel-shared/volumes.c  | 10 +++-----
 mkfs/main.c              |  8 +++---
 tune/main.c              |  2 +-
 17 files changed, 136 insertions(+), 125 deletions(-)

-- 
2.38.1


             reply	other threads:[~2023-06-13 10:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 10:26 Anand Jain [this message]
2023-06-13 10:26 ` [PATCH 1/6] btrfs-progs: check_mounted_where: declare is_btrfs as bool Anand Jain
2023-06-13 10:26 ` [PATCH 2/6] btrfs-progs: rename struct open_ctree_flags to open_ctree_args Anand Jain
2023-06-13 10:40   ` Qu Wenruo
2023-06-13 10:26 ` [PATCH 3/6] btrfs-progs: drop open_ctree_flags in cmd_inspect_dump_tree Anand Jain
2023-06-13 10:41   ` Qu Wenruo
2023-06-13 10:26 ` [PATCH 4/6] btrfs-progs: device_list_add: optimize arguments drop devid Anand Jain
2023-06-13 10:26 ` [PATCH 5/7] btrfs-progs: factor out btrfs_scan_argv_devices Anand Jain
2023-06-13 10:49   ` Qu Wenruo
2023-06-13 11:12     ` Anand Jain
2023-06-13 10:26 ` [PATCH 6/6] btrfs-progs: refactor check_where_mounted with noscan argument Anand Jain
2023-06-28 22:24 ` [PATCH 0/6 v3] btrfs-progs: cleanup and preparatory around device scan David Sterba

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.1686484067.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.