From: Chris Mason <clm@fb.com>
To: David Sterba <dsterba@suse.cz>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL] Btrfs fixes for 4.8, part 2
Date: Tue, 23 Aug 2016 08:14:38 -0400 [thread overview]
Message-ID: <20160823121437.GA74907@clm-mbp> (raw)
In-Reply-To: <20160823110237.GI16983@twin.jikos.cz>
On Tue, Aug 23, 2016 at 01:02:37PM +0200, David Sterba wrote:
>On Wed, Aug 17, 2016 at 05:11:13PM +0200, David Sterba wrote:
>> Hi,
>>
>> this is a short series, mostly small fixes that did not make it to the first
>> round. Please pull, thanks.
>
>As you did not pick this pull request, I'll prepare another one with
>more patches, based on this branch.
Thanks Dave, I've been trying to nail down this fsync memory corruption
problem. But, I'll send a pull on Thursday/Friday with or without an
fsync patch.
-chris
prev parent reply other threads:[~2016-08-23 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 15:11 [PULL] Btrfs fixes for 4.8, part 2 David Sterba
2016-08-23 11:02 ` David Sterba
2016-08-23 12:14 ` 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=20160823121437.GA74907@clm-mbp \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).