From: David Sterba <dsterba@suse.cz>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: [PULL] [PATCH 0/8] Cleanups, 3.16 or later
Date: Fri, 20 Jun 2014 13:01:49 +0200 [thread overview]
Message-ID: <cover.1403260619.git.dsterba@suse.cz> (raw)
Hi Chris,
this is a set of whole-directory changes that have low impact on stability
(xfstests passed), but touch almost all files aiming for simpler code.
I did not catch the merge window train, so I'm leaving it to your consideration
if you add it to the upcomming pull request(s).
I'm sending this as a pull request combined with patches to mailinglist.
Top commit cbe260e207c57843c1dcd550f9adbab7507945c6
based on 8408c716d7a4ddd5954ce33f53a7d3cd2876cf65 (current for-linus)
Available in the git repository at:
git://repo.or.cz/linux-2.6/btrfs-unstable.git cleanups-for-3.16
Thanks.
David Sterba (8):
btrfs: remove obsolete comment in btrfs_clean_one_deleted_snapshot
btrfs: clenaup: don't call btrfs_release_path before free_path
btrfs: cleanup ino cache members of btrfs_root
btrfs: make close_ctree return void
btrfs: kill the key type accessor helpers
btrfs: use nodesize everywhere, kill leafsize
btrfs: clean away stripe_align helper
btrfs: use DIV_ROUND_UP instead of open-coded variants
fs/btrfs/backref.c | 12 +++---
fs/btrfs/check-integrity.c | 16 +--------
fs/btrfs/compression.c | 10 ++---
fs/btrfs/ctree.c | 18 +++++-----
fs/btrfs/ctree.h | 31 +++++-----------
fs/btrfs/delayed-inode.c | 8 ++--
fs/btrfs/dir-item.c | 12 +++---
fs/btrfs/disk-io.c | 84 +++++++++++++++++++------------------------
fs/btrfs/disk-io.h | 2 +-
fs/btrfs/export.c | 4 +-
fs/btrfs/extent-tree.c | 53 +++++++++++----------------
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/file-item.c | 12 +++---
fs/btrfs/file.c | 25 ++++++-------
fs/btrfs/free-space-cache.c | 17 ++++-----
fs/btrfs/inode-item.c | 12 +++---
fs/btrfs/inode-map.c | 68 +++++++++++++++++-----------------
fs/btrfs/inode.c | 28 +++++++-------
fs/btrfs/ioctl.c | 23 ++++++------
fs/btrfs/lzo.c | 3 +-
fs/btrfs/orphan.c | 4 +-
fs/btrfs/print-tree.c | 4 +-
fs/btrfs/qgroup.c | 6 +--
fs/btrfs/raid56.c | 8 ++--
fs/btrfs/reada.c | 2 +-
fs/btrfs/relocation.c | 22 +++++------
fs/btrfs/scrub.c | 19 +---------
fs/btrfs/super.c | 8 +----
fs/btrfs/transaction.c | 7 +---
fs/btrfs/tree-log.c | 8 ++--
fs/btrfs/volumes.c | 4 +-
fs/btrfs/xattr.c | 4 +-
fs/btrfs/zlib.c | 3 +-
33 files changed, 228 insertions(+), 311 deletions(-)
--
1.7.9
next reply other threads:[~2014-06-20 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 11:01 David Sterba [this message]
2014-06-20 11:01 ` [PATCH 1/8] btrfs: remove obsolete comment in btrfs_clean_one_deleted_snapshot David Sterba
2014-06-20 11:02 ` [PATCH 2/8] btrfs: clenaup: don't call btrfs_release_path before free_path David Sterba
2014-06-20 11:02 ` [PATCH 3/8] btrfs: cleanup ino cache members of btrfs_root David Sterba
2014-06-20 11:02 ` [PATCH 4/8] btrfs: make close_ctree return void David Sterba
2014-06-20 11:02 ` [PATCH 5/8] btrfs: kill the key type accessor helpers David Sterba
2014-06-20 11:02 ` [PATCH 6/8] btrfs: use nodesize everywhere, kill leafsize David Sterba
2014-06-20 11:02 ` [PATCH 7/8] btrfs: clean away stripe_align helper David Sterba
2014-06-20 11:03 ` [PATCH 8/8] btrfs: use DIV_ROUND_UP instead of open-coded variants David Sterba
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=cover.1403260619.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--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).