All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Sam Thursfield <sam.thursfield@codethink.co.uk>,
	Anand Jain <anand.jain@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	<johannes.hirte@datenkhaos.de>
Subject: Re: [PATCH] Revert "Btrfs: device_list_add() should not update list when
Date: Fri, 19 Sep 2014 09:59:12 -0400	[thread overview]
Message-ID: <541C36B0.4030906@fb.com> (raw)
In-Reply-To: <541C33D8.5030000@codethink.co.uk>

On 09/19/2014 09:47 AM, Sam Thursfield wrote:
> On 18/09/14 16:00, Chris Mason wrote:
>>
>> Johannes and Sam, could you please confirm this patch fixes your mount
>> regression for now?  Anand, please make sure I kept the generation check
>> properly.
> 
> I've just tested this patch on top of 3.17-rc5 and it fixes the issue
> for me.
> 

Perfect, thanks.

-chris


      reply	other threads:[~2014-09-19 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 15:00 [PATCH] Revert "Btrfs: device_list_add() should not update list when Chris Mason
2014-09-19 10:21 ` Anand Jain
2014-09-19 13:47 ` Sam Thursfield
2014-09-19 13:59   ` Chris Mason [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=541C36B0.4030906@fb.com \
    --to=clm@fb.com \
    --cc=anand.jain@oracle.com \
    --cc=johannes.hirte@datenkhaos.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sam.thursfield@codethink.co.uk \
    /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.