From: Jeff Liu <jeff.liu@oracle.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: Mike Fleetwood <mike.fleetwood@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs_print_tree?
Date: Sun, 01 Jul 2012 18:16:55 +0800 [thread overview]
Message-ID: <4FF02397.3040002@oracle.com> (raw)
In-Reply-To: <CAEH94LhNWsye0HsDjroeRQ76vLkmKSUwYwzGKjfbJCeO-wLEuw@mail.gmail.com>
On 07/01/2012 05:49 PM, Zhi Yong Wu wrote:
> On Sun, Jul 1, 2012 at 5:41 PM, Mike Fleetwood
> <mike.fleetwood@googlemail.com> wrote:
>> On 1 July 2012 05:53, Zhi Yong Wu <zwu.kernel@gmail.com> wrote:
>>> HI,
>>>
>>> Do anyone know where btrfs_print_tree is invoked? thanks.
>>>
>>> --
>>> Regards,
>>>
>>> Zhi Yong Wu
>>
>> Is this the answer you are after?
>>
>> $ grep -r btrfs_print_tree fs/btrfs/
>> fs/btrfs/print-tree.c:void btrfs_print_tree(struct btrfs_root *root,
>> struct extent_buffer *c)
>> fs/btrfs/print-tree.c: btrfs_print_tree(root, next);
>> fs/btrfs/print-tree.h:void btrfs_print_tree(struct btrfs_root *root,
>> struct extent_buffer *t);
> No, i also did as this, but didn't find out who will invoke this
> function. From above output, we only saw that it invokes itself one
> time.
Looks this is a helper routine exported to btrfs-progs previously, it is
used by debug-tree, quick-test, etc...
But this function has been implemented at btrfs-progs now, maybe it
could be safely removed from kernel, not sure. :)
Thanks,
-Jeff
>
>>
>> Mike
>
>
>
next prev parent reply other threads:[~2012-07-01 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 4:53 btrfs_print_tree? Zhi Yong Wu
2012-07-01 9:41 ` btrfs_print_tree? Mike Fleetwood
2012-07-01 9:49 ` btrfs_print_tree? Zhi Yong Wu
2012-07-01 10:15 ` btrfs_print_tree? Andreas Philipp
2012-07-01 10:16 ` Jeff Liu [this message]
2012-07-01 10:24 ` btrfs_print_tree? Andreas Philipp
2012-07-01 10:38 ` btrfs_print_tree? Zhi Yong Wu
2012-07-04 15:51 ` btrfs_print_tree? 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=4FF02397.3040002@oracle.com \
--to=jeff.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mike.fleetwood@googlemail.com \
--cc=zwu.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).