Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Jeff Mahoney <jeffm@suse.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: opencode chunk locking, remove helpers
Date: Thu, 6 Oct 2016 09:41:35 +0200	[thread overview]
Message-ID: <20161006074134.GG6576@twin.jikos.cz> (raw)
In-Reply-To: <50a2d25f-844b-651c-4d55-2a5ea66d178e@suse.com>

On Wed, Oct 05, 2016 at 02:41:24PM -0400, Jeff Mahoney wrote:
> On 10/5/16 8:23 AM, David Sterba wrote:
> > The helpers are trivial and we don't use them consistently.
> 
> This one is going to conflict with the root->fs_info removal patchset in
> every chunk since the helper does nothing with the root.  Otherwise, the
> idea is sound.

No problem, I'll refresh and resend after the fsinfo/root series.

      reply	other threads:[~2016-10-06  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 12:23 [PATCH] btrfs: opencode chunk locking, remove helpers David Sterba
2016-10-05 18:41 ` Jeff Mahoney
2016-10-06  7:41   ` David Sterba [this message]

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=20161006074134.GG6576@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.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