From: Josef Bacik <jbacik@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Question about e8569813849b5da394a195c7e76b4faa452b12d1
Date: Wed, 8 Oct 2008 16:59:48 -0400 [thread overview]
Message-ID: <20081008205947.GA18375@unused.rdu.redhat.com> (raw)
Hello,
Is there a reason
- if (search_end == (u64)-1)
- search_end = btrfs_super_total_bytes(&info->super_copy);
happened in the commit from $SUBJECT? If its just a mistake thats fine I'll add
it back with my current patch, but if there is a reason it needed to go then I
need to know that too so I can figure out a different way to do what I want to
do. Thanks,
Josef
next reply other threads:[~2008-10-08 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 20:59 Josef Bacik [this message]
2008-10-09 0:14 ` Question about e8569813849b5da394a195c7e76b4faa452b12d1 Chris Mason
2008-10-09 1:47 ` Yan Zheng
2008-10-09 10:49 ` Josef Bacik
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=20081008205947.GA18375@unused.rdu.redhat.com \
--to=jbacik@redhat.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