From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz, clm@fb.com
Subject: Re: [PATCH 1/2] btrfs-progs: introduce btrfs_register_all_device()
Date: Thu, 30 Oct 2014 15:33:10 +0100 [thread overview]
Message-ID: <20141030143310.GA21354@twin.jikos.cz> (raw)
In-Reply-To: <1413334270-25766-1-git-send-email-anand.jain@oracle.com>
On Wed, Oct 15, 2014 at 08:51:09AM +0800, Anand Jain wrote:
> --- a/volumes.c
> +++ b/volumes.c
> @@ -30,6 +30,7 @@
> #include "print-tree.h"
> #include "volumes.h"
> #include "math.h"
> +#include "utils.h"
>
> struct stripe {
> struct btrfs_device *dev;
> @@ -1533,6 +1534,30 @@ btrfs_find_device_by_devid(struct btrfs_fs_devices *fs_devices,
> return NULL;
> }
>
> +/*
> + * Register all devices in the fs_uuid list created in the user
> + * space. Ensure btrfs_scan_lblkid() is called before this func.
> + */
> +int btrfs_register_all_devices(void)
I think this belongs to utils.c, btrfs_register_one_device is also there
and it is an API funcion for the commands. You can use
btrfs_scanned_uuids() to get to the fs_uuids variable that's locally
defined in volumes.c .
next prev parent reply other threads:[~2014-10-30 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 0:51 [PATCH 1/2] btrfs-progs: introduce btrfs_register_all_device() Anand Jain
2014-10-15 0:51 ` [PATCH 2/2] btrfs-progs: optimize btrfs_scan_lblkid() for multiple calls Anand Jain
2014-10-23 6:30 ` [PATCH 2/2 v2] " Anand Jain
2014-10-30 14:18 ` David Sterba
2014-10-31 1:38 ` Anand Jain
2014-10-31 3:19 ` [PATCH 2/2 v3] " Anand Jain
2014-10-30 14:33 ` David Sterba [this message]
2014-10-31 2:28 ` [PATCH 1/2] btrfs-progs: introduce btrfs_register_all_device() Anand Jain
2014-10-31 4:11 ` [PATCH 1/2 v4] " Anand Jain
2014-10-31 4:11 ` [PATCH 2/2 v4] btrfs-progs: optimize btrfs_scan_lblkid() for multiple calls Anand Jain
2014-10-31 9:08 ` Karel Zak
2014-10-31 11:04 ` Anand Jain
2014-11-11 11:47 ` Karel Zak
2014-11-14 16:51 ` David Sterba
2014-11-28 9:33 ` Karel Zak
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=20141030143310.GA21354@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=clm@fb.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).