From: Chris Mason <clm@fb.com>
To: David Sterba <dsterba@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL] Btrfs for 4.8, part 1
Date: Tue, 26 Jul 2016 16:02:42 -0400 [thread overview]
Message-ID: <20160726200240.GA25382@clm-mbp.thefacebook.com> (raw)
In-Reply-To: <cover.1469542859.git.dsterba@suse.com>
On Tue, Jul 26, 2016 at 04:41:57PM +0200, David Sterba wrote:
>Hi,
>
>please pull the following patches to 4.8. There are mostly small independent
>fixes or cleanups. The branch is based on your current 'next' because of patch
>dependencies. I don't want to start it on 4.7-rc6 as the merge conflicts would
>be many and not trivial.
>
>There are a few more patches that were sent but haven't received enough reviews
>so I may send one more pull request should this change.
Thanks Dave, I have this one in testing.
-chris
prev parent reply other threads:[~2016-07-26 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:41 [PULL] Btrfs for 4.8, part 1 David Sterba
2016-07-26 20:02 ` 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=20160726200240.GA25382@clm-mbp.thefacebook.com \
--to=clm@fb.com \
--cc=dsterba@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;
as well as URLs for NNTP newsgroup(s).