From: Chris Mason <chris.mason@oracle.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix btrfs_read_block_groups return value
Date: Thu, 12 Feb 2009 09:49:35 -0500 [thread overview]
Message-ID: <1234450175.8300.1.camel@think.oraclecorp.com> (raw)
In-Reply-To: <4993808C.20000@suse.com>
On Wed, 2009-02-11 at 20:51 -0500, Jeff Mahoney wrote:
> btrfs_read_block_groups returns an ambiguous value. Whether it finds
> a block group or not, it will return -ENOENT. find_first_block_group
> will eventually return -ENOENT when it reaches past the last block
> group, and that is what is returned to the caller.
Jeff, thanks for starting on all of this. Could I talk you into setting
up a git tree? I think you're going to have a long stream of patches
and merging them with my trees is going to be much easier over git.
-chris
next prev parent reply other threads:[~2009-02-12 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 1:51 [PATCH] btrfs: fix btrfs_read_block_groups return value Jeff Mahoney
2009-02-12 1:57 ` [PATCH #2] " Jeff Mahoney
2009-02-12 14:49 ` Chris Mason [this message]
2009-02-12 14:54 ` [PATCH] " Jeff Mahoney
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=1234450175.8300.1.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=jeffm@suse.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