From: Chris Mason <clm@fb.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, Filipe Manana <fdmanana@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Send fixes for 4.2
Date: Tue, 9 Jun 2015 09:02:11 -0400 [thread overview]
Message-ID: <5576E3D3.40008@fb.com> (raw)
In-Reply-To: <55769308.1070803@cn.fujitsu.com>
On 06/09/2015 03:17 AM, Qu Wenruo wrote:
> Hi, Chris and Filipe.
>
> Would you consider the patch from Filipe to be merged into 4.2?
>
> [PATCH] Btrfs: avoid syncing log in the fast fsync path when not necessary
>
> https://patchwork.kernel.org/patch/6138811/
>
>
> The performance regression is already in 4.1, and I really don't like to
> see the performance regression be there for 4.2.
>
> So please consider include this patch in 4.2 merge window.
Thanks Qu, pulling this in now.
-chris
prev parent reply other threads:[~2015-06-09 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 3:15 [GIT PULL] Send fixes for 4.2 Filipe Manana
2015-06-03 3:15 ` [PATCH 1/2 RESEND] Btrfs: incremental send, don't delay directory renames unnecessarily Filipe Manana
2015-06-03 3:15 ` [PATCH 2/2 RESEND] Btrfs: incremental send, check if orphanized dir inode needs delayed rename Filipe Manana
2015-06-04 2:45 ` [GIT PULL] Send fixes for 4.2 Chris Mason
2015-06-09 7:17 ` Qu Wenruo
2015-06-09 13: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=5576E3D3.40008@fb.com \
--to=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/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