From: Chris Mason <clm@fb.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL REQUEST][PATCH 0/2] Small fixes for 4.3 merge windows
Date: Wed, 14 Oct 2015 21:45:15 -0400 [thread overview]
Message-ID: <20151015014515.GG4890@ret.masoncoding.com> (raw)
In-Reply-To: <1444807573-29853-1-git-send-email-quwenruo@cn.fujitsu.com>
On Wed, Oct 14, 2015 at 03:26:11PM +0800, Qu Wenruo wrote:
> Hi Chris,
>
> This pull is quite a small one, with 2 small and safe patches.
>
> The first one is a fix that get missing in 4.2 merge windows.
> Just remove an empty header I created in qgroup rework.
>
> The other one is found in qgroup reserve rework, but that's also very
> small and safe, with test case submitted:
> https://patchwork.kernel.org/patch/7292921/
Thanks Qu, I'll get these tested.
-chris
prev parent reply other threads:[~2015-10-15 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 7:26 [PULL REQUEST][PATCH 0/2] Small fixes for 4.3 merge windows Qu Wenruo
2015-10-14 7:26 ` [PATCH 1/2] btrfs: Remove empty header file extent-tree.h Qu Wenruo
2015-10-14 7:26 ` [PATCH 2/2] btrfs: Avoid truncate tailing page if fallocate range doesn't exceed inode size Qu Wenruo
2015-10-15 1:45 ` 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=20151015014515.GG4890@ret.masoncoding.com \
--to=clm@fb.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;
as well as URLs for NNTP newsgroup(s).