From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>, clm@fb.com
Subject: [PULL] [PATCH 00/11] Cleanups for 4.1
Date: Wed, 25 Feb 2015 19:24:31 +0100 [thread overview]
Message-ID: <cover.1424880058.git.dsterba@suse.cz> (raw)
Hi,
a few cleanups that accumulated over time. No real fixes but there are changes
that may touch functionality (no fstests complaints though).
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git cleanups-for-4.1
all merged together, but are also available in the following topic branches
based on current for-linus branch.
cleanup/sched
cleanup/divs
cleanup/kmalloc-array
cleanup/shadow-vars
cleanup/initializers
David Sterba (11):
btrfs: need_resched not needed with cond_resched
btrfs: use cond_resched_lock where possible
btrfs: cleanup 64bit/32bit divs, compile time constants
btrfs: cleanup 64bit/32bit divs, provably bounded values
btrfs: replace remaining do_div calls with div_u64 variants
btrfs: cleanup, use correct type in div_u64_rem
btrfs: cleanup, use kmalloc_array/kcalloc array helpers
btrfs: remove shadowing variables in __btrfs_buffered_write
btrfs: switch helper macros to static inlines in sysfs.h
btrfs: remove shadowing variables in __btrfs_map_block
btrfs: use explicit initializer for seq_elem
fs/btrfs/backref.c | 4 +--
fs/btrfs/check-integrity.c | 4 +--
fs/btrfs/compression.c | 2 +-
fs/btrfs/ctree.c | 9 +++--
fs/btrfs/ctree.h | 2 ++
fs/btrfs/dev-replace.c | 6 ++--
fs/btrfs/disk-io.c | 4 +--
fs/btrfs/extent-tree.c | 21 ++++++------
fs/btrfs/file-item.c | 4 +--
fs/btrfs/file.c | 12 +++----
fs/btrfs/free-space-cache.c | 34 ++++++++-----------
fs/btrfs/inode.c | 2 +-
fs/btrfs/ioctl.c | 4 +--
fs/btrfs/math.h | 6 ++--
fs/btrfs/qgroup.c | 6 ++--
fs/btrfs/raid56.c | 3 +-
fs/btrfs/scrub.c | 23 ++++++-------
fs/btrfs/super.c | 2 +-
fs/btrfs/sysfs.h | 22 ++++++++++---
fs/btrfs/transaction.c | 7 ++--
fs/btrfs/volumes.c | 80 ++++++++++++++++++++++-----------------------
21 files changed, 125 insertions(+), 132 deletions(-)
--
2.1.3
next reply other threads:[~2015-02-25 18:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:24 David Sterba [this message]
2015-02-25 18:24 ` [PATCH 01/11] btrfs: need_resched not needed with cond_resched David Sterba
2015-02-25 18:24 ` [PATCH 02/11] btrfs: use cond_resched_lock where possible David Sterba
2015-02-25 18:24 ` [PATCH 03/11] btrfs: cleanup 64bit/32bit divs, compile time constants David Sterba
2015-02-25 18:24 ` [PATCH 04/11] btrfs: cleanup 64bit/32bit divs, provably bounded values David Sterba
2015-02-25 18:24 ` [PATCH 05/11] btrfs: replace remaining do_div calls with div_u64 variants David Sterba
2015-02-25 18:24 ` [PATCH 06/11] btrfs: cleanup, use correct type in div_u64_rem David Sterba
2015-02-25 18:24 ` [PATCH 07/11] btrfs: cleanup, use kmalloc_array/kcalloc array helpers David Sterba
2015-02-25 18:24 ` [PATCH 08/11] btrfs: remove shadowing variables in __btrfs_buffered_write David Sterba
2015-02-25 18:25 ` [PATCH 09/11] btrfs: switch helper macros to static inlines in sysfs.h David Sterba
2015-02-25 18:25 ` [PATCH 10/11] btrfs: remove shadowing variables in __btrfs_map_block David Sterba
2015-02-25 18:25 ` [PATCH 11/11] btrfs: use explicit initializer for seq_elem David Sterba
2015-02-26 1:39 ` [PULL] [PATCH 00/11] Cleanups for 4.1 Zhao Lei
2015-02-26 17:46 ` David Sterba
2015-03-03 16:30 ` 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.1424880058.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).