linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>, <clm@fb.com>
Subject: [PULL REQUEST][PATCH 0/2] Small fixes for 4.3 merge windows
Date: Wed, 14 Oct 2015 15:26:11 +0800	[thread overview]
Message-ID: <1444807573-29853-1-git-send-email-quwenruo@cn.fujitsu.com> (raw)

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/

I was planning to include two qgroup rescan fix patches, but doesn't get
further comment from David, so they may be delayed to 4.4, with qgroup
reserve rework.

Thanks,
Qu

Qu Wenruo (2):
  btrfs: Remove empty header file extent-tree.h
  btrfs: Avoid truncate tailing page if fallocate range doesn't exceed
    inode size

 fs/btrfs/extent-tree.h | 0
 fs/btrfs/file.c        | 2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)
 delete mode 100644 fs/btrfs/extent-tree.h

-- 
2.6.1


             reply	other threads:[~2015-10-14  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  7:26 Qu Wenruo [this message]
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 ` [PULL REQUEST][PATCH 0/2] Small fixes for 4.3 merge windows Chris Mason

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=1444807573-29853-1-git-send-email-quwenruo@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=clm@fb.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).