All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: refactor btrfs_check_data_free_space
Date: Tue, 29 Sep 2009 13:12:17 -0400	[thread overview]
Message-ID: <20090929171217.GC2650@think> (raw)
In-Reply-To: <1253913056-8385-1-git-send-email-sage@newdream.net>

On Fri, Sep 25, 2009 at 02:10:55PM -0700, Sage Weil wrote:
> Pull out the actual free space check, so setting an inode's initial
> space_info is done by the caller instead of a wonky goto.
> 

Hi Sage,

I've just pushed out an updated enospc branch.  Could you please verify
your patches against it?  If you and Josef are happy with them, I'll
pull them in.

-chris


  parent reply	other threads:[~2009-09-29 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 21:10 [PATCH 1/2] Btrfs: refactor btrfs_check_data_free_space Sage Weil
2009-09-25 21:10 ` [PATCH 2/2] Btrfs: add TRANS_RESV_START ioctl to check/reserve free space on transaction start Sage Weil
2009-09-29 17:12 ` Chris Mason [this message]
2009-09-29 18:49   ` [PATCH 1/2] Btrfs: refactor btrfs_check_data_free_space Sage Weil

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=20090929171217.GC2650@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sage@newdream.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.