From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 00/14] Misc cleanups for 4.19
Date: Fri, 29 Jun 2018 10:56:37 +0200 [thread overview]
Message-ID: <cover.1530262400.git.dsterba@suse.com> (raw)
Minor interface/API and other safe cleanups.
David Sterba (14):
btrfs: simplify some assignments of inode numbers
btrfs: simplify pointer chasing of local fs_info variables
btrfs: use copy_page for copying pages instead of memcpy
btrfs: prune unused includes
btrfs: pass only eb to num_extent_pages
btrfs: switch types to int when counting eb pages
btrfs: open-code bio_set_op_attrs
btrfs: raid56: add new helper for starting async work
btrfs: raid56: use new helper for async_rmw_stripe
btrfs: raid56: use new helper for async_read_rebuild
btrfs: raid56: use new helper for async_scrub_parity
btrfs: raid56: merge rbio_is_full helpers
btrfs: raid56: don't lock stripe cache table when freeing
btrfs: raid56: catch errors from full_stripe_write
fs/btrfs/check-integrity.c | 2 +-
fs/btrfs/compression.c | 8 +--
fs/btrfs/delayed-inode.c | 4 +-
fs/btrfs/dev-replace.c | 5 --
fs/btrfs/disk-io.c | 4 +-
fs/btrfs/extent-tree.c | 6 +-
fs/btrfs/extent_io.c | 70 +++++++++++-----------
fs/btrfs/extent_io.h | 6 +-
fs/btrfs/file-item.c | 2 +-
fs/btrfs/file.c | 17 +++---
fs/btrfs/free-space-cache.c | 11 ++--
fs/btrfs/inode-map.c | 1 -
fs/btrfs/inode.c | 24 ++++----
fs/btrfs/ioctl.c | 5 --
fs/btrfs/ordered-data.c | 1 -
fs/btrfs/raid56.c | 112 +++++++++++-------------------------
fs/btrfs/reada.c | 1 -
fs/btrfs/scrub.c | 6 +-
fs/btrfs/struct-funcs.c | 1 -
fs/btrfs/super.c | 3 -
fs/btrfs/sysfs.c | 2 -
fs/btrfs/tree-log.c | 6 +-
fs/btrfs/volumes.c | 3 -
23 files changed, 109 insertions(+), 191 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-29 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:56 David Sterba [this message]
2018-06-29 8:56 ` [PATCH 01/14] btrfs: simplify some assignments of inode numbers David Sterba
2018-06-29 8:56 ` [PATCH 02/14] btrfs: simplify pointer chasing of local fs_info variables David Sterba
2018-06-29 8:56 ` [PATCH 03/14] btrfs: use copy_page for copying pages instead of memcpy David Sterba
2018-06-29 8:56 ` [PATCH 04/14] btrfs: prune unused includes David Sterba
2018-06-29 8:56 ` [PATCH 05/14] btrfs: pass only eb to num_extent_pages David Sterba
2018-06-29 9:08 ` Nikolay Borisov
2018-06-29 14:29 ` David Sterba
2018-06-29 15:12 ` Nikolay Borisov
2018-06-29 8:56 ` [PATCH 06/14] btrfs: switch types to int when counting eb pages David Sterba
2018-06-29 8:56 ` [PATCH 07/14] btrfs: open-code bio_set_op_attrs David Sterba
2018-06-29 8:56 ` [PATCH 08/14] btrfs: raid56: add new helper for starting async work David Sterba
2018-06-29 8:56 ` [PATCH 09/14] btrfs: raid56: use new helper for async_rmw_stripe David Sterba
2018-06-29 8:57 ` [PATCH 10/14] btrfs: raid56: use new helper for async_read_rebuild David Sterba
2018-06-29 8:57 ` [PATCH 11/14] btrfs: raid56: use new helper for async_scrub_parity David Sterba
2018-06-29 8:57 ` [PATCH 12/14] btrfs: raid56: merge rbio_is_full helpers David Sterba
2018-06-29 8:57 ` [PATCH 13/14] btrfs: raid56: don't lock stripe cache table when freeing David Sterba
2018-06-29 15:18 ` David Sterba
2018-06-29 8:57 ` [PATCH 14/14] btrfs: raid56: catch errors from full_stripe_write 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.1530262400.git.dsterba@suse.com \
--to=dsterba@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.