From: Gu Jinxiang <gujx@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: <linux-btrfs@vger.kernel.org>
Subject: [PATCH v2 0/2] btrfs-progs: Update btrfs-progs to match kernel sources
Date: Thu, 11 Jan 2018 18:11:06 +0800 [thread overview]
Message-ID: <1515665468-7450-1-git-send-email-gujx@cn.fujitsu.com> (raw)
In-Reply-To: <1512471667-8555-1-git-send-email-gujx@cn.fujitsu.com>
v2->v1:
Modify btrfs-progs by refer to the two patches list below:
commit a717531942f4 ("Btrfs: do less aggressive btree readahead")
commit e4058b54d1e4 ("btrfs: cleanup, use enum values for btrfs_path reada")
Gu Jinxiang (2):
btrfs-progs: do less aggressive btree readahead
btrfs-progs: cleanup, use enum values for btrfs_path reada
cmds-restore.c | 4 ++--
ctree.c | 33 +++++++++++----------------------
ctree.h | 2 +-
extent-tree.c | 12 ++++++------
free-space-tree.c | 2 +-
qgroup-verify.c | 2 +-
volumes.c | 4 ++--
7 files changed, 24 insertions(+), 35 deletions(-)
--
2.14.3
next prev parent reply other threads:[~2018-01-11 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 11:01 [PATCH] btrfs-progs: use enum instead of constant value Gu Jinxiang
2018-01-11 10:11 ` Gu Jinxiang [this message]
2018-01-11 10:11 ` [PATCH v2 1/2] btrfs-progs: do less aggressive btree readahead Gu Jinxiang
2018-01-11 10:11 ` [PATCH v2 2/2] btrfs-progs: cleanup, use enum values for btrfs_path reada Gu Jinxiang
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=1515665468-7450-1-git-send-email-gujx@cn.fujitsu.com \
--to=gujx@cn.fujitsu.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).