From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: [PATCH v2 0/3] btrfs-progs: Split lowmem mode check to its own
Date: Thu, 1 Feb 2018 14:45:38 +0800 [thread overview]
Message-ID: <20180201064541.14603-1-wqu@suse.com> (raw)
As usual, the main part is over 500K so the biggest patch won't reach
mail list.
Please fetch the whole branch from github:
https://github.com/adam900710/btrfs-progs/tree/split_check
This update rebased (the truth is, it's re-created other than rebase)
the branch to David's devel branch, whose head is:
commit cfe255515ae0a27fdd8e612a884b94ffb703acdf (david/devel)
Author: Qu Wenruo <wqu@suse.com>
Date: Thu Jan 18 16:38:23 2018 +0800
btrfs-progs: check: Move reset_cached_block_groups to check/common.c
Reviewed-by: Su Yue <suy.fnst@cn.fujitsu.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
Despite the update, a new patch is introduced, to address the tons of
BORING errors and warning from checkpatch.pl.
Qu Wenruo (3):
btrfs-progs: check: Move lowmem check code to its own
check/lowmem.[ch]
btrfs-progs: check/lowmem: Cleanup unnecessary _v2 suffix
btrfs-progs: check: Cleanup all checkpatch error and warning
Makefile | 2 +-
check/lowmem.c | 4579 ++++++++++++++++++++
check/lowmem.h | 5 +
check/main.c | 12772 ++++++++++++++++++-------------------------------------
4 files changed, 8694 insertions(+), 8664 deletions(-)
create mode 100644 check/lowmem.c
--
2.16.1
next reply other threads:[~2018-02-01 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 6:45 Qu Wenruo [this message]
2018-02-01 6:45 ` [PATCH v2 2/3] btrfs-progs: check/lowmem: Cleanup unnecessary _v2 suffix Qu Wenruo
2018-02-01 6:45 ` [PATCH v2 3/3] btrfs-progs: check: Cleanup all checkpatch error and warning Qu Wenruo
2018-02-01 7:08 ` Su Yue
2018-02-01 7:48 ` Qu Wenruo
2018-02-01 8:28 ` Nikolay Borisov
2018-02-01 15:06 ` David Sterba
2018-02-01 8:36 ` Nikolay Borisov
2018-02-01 9:20 ` Qu Wenruo
2018-02-01 16:05 ` [PATCH v2 0/3] btrfs-progs: Split lowmem mode check to its own David Sterba
2018-02-02 1:36 ` Qu Wenruo
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=20180201064541.14603-1-wqu@suse.com \
--to=wqu@suse.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).