From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] btrfs: find_device cleanups
Date: Fri, 18 Jan 2019 18:33:30 +0100 [thread overview]
Message-ID: <20190118173330.GD2900@twin.jikos.cz> (raw)
In-Reply-To: <1547739153-6916-1-git-send-email-anand.jain@oracle.com>
On Thu, Jan 17, 2019 at 11:32:27PM +0800, Anand Jain wrote:
> find_device and its helper functions are as below
>
> btrfs_find_device_by_devspec()
> btrfs_find_device_missing_or_by_path()
> btrfs_find_device_by_path()
> btrfs_find_device()
> find_device()
>
> Its quite confusing and too fragmented.
>
> In this patch-set..
> 1/6 and 2/6 -- btrfs_find_device_missing_or_by_path() is collapsed into
> btrfs_find_device_by_devspec() and cleanup the surviving function.
>
> 3/6 -- rename btrfs_find_device_by_path() to find_device_by_superblock().
>
> 4/6 and 5/6 -- collapses find_device() into btrfs_find_device().
>
> 6/6 refactors btrfs_find_device() to return standard error code.
>
> Resulting in..
>
> btrfs_find_device():
> Mainly used to get struct btrfs_device internally for a given devid
> and or uuid and also helper function for btrfs_find_device_by_devspec().
>
> btrfs_find_device_by_devspec() and a helper function find_device_by_superblock():
> Is mainly to retrieve the struct btrfs_device of a userland given device_path.
>
> Anand Jain (6):
> btrfs: merge btrfs_find_device_missing_or_by_path() into parent
> btrfs: cleanup btrfs_find_device_by_devspec()
> btrfs: rename btrfs_find_device_by_path()
> btrfs: refactor btrfs_find_device() take fs_devices as argument
> btrfs: merge btrfs_find_device() and find_device()
> btrfs: refactor btrfs_find_device() return error code
1,2,4, applied, please update 5 and resend. Thanks.
next prev parent reply other threads:[~2019-01-18 17:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:32 [PATCH 0/6] btrfs: find_device cleanups Anand Jain
2019-01-17 15:32 ` [PATCH 1/6] btrfs: merge btrfs_find_device_missing_or_by_path() into parent Anand Jain
2019-01-17 15:57 ` David Sterba
2019-01-17 15:32 ` [PATCH 2/6] btrfs: cleanup btrfs_find_device_by_devspec() Anand Jain
2019-01-17 15:57 ` David Sterba
2019-01-17 15:32 ` [PATCH 3/6] btrfs: rename btrfs_find_device_by_path() Anand Jain
2019-01-17 15:54 ` David Sterba
2019-01-18 6:13 ` Anand Jain
2019-01-18 17:05 ` David Sterba
2019-01-17 15:32 ` [PATCH 4/6] btrfs: refactor btrfs_find_device() take fs_devices as argument Anand Jain
2019-01-17 15:58 ` David Sterba
2019-01-17 15:32 ` [PATCH 5/6] btrfs: merge btrfs_find_device() and find_device() Anand Jain
2019-01-17 15:51 ` David Sterba
2019-01-19 6:48 ` [PATCH 5/6 v2] " Anand Jain
2019-01-23 5:28 ` Anand Jain
2019-01-28 18:44 ` David Sterba
2019-01-17 15:32 ` [PATCH 6/6] btrfs: refactor btrfs_find_device() return error code Anand Jain
2019-01-17 15:49 ` David Sterba
2019-01-18 6:13 ` Anand Jain
2019-01-18 17:20 ` David Sterba
2019-01-18 17:33 ` David Sterba [this message]
2019-01-19 6:54 ` [PATCH 0/6] btrfs: find_device cleanups 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=20190118173330.GD2900@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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).