From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/6] Minor cleanups
Date: Tue, 18 Jun 2019 20:00:00 +0200 [thread overview]
Message-ID: <cover.1560880630.git.dsterba@suse.com> (raw)
A few misc cleanups selected from my other branche, all should be safe.
David Sterba (6):
btrfs: use common helpers for eb leak messages
btrfs: use common helpers for extent IO state insertion messages
btrfs: drop default value assignments in enums
btrfs: use raid_attr to adjust minimal stripe size in
btrfs_calc_avail_data_space
btrfs: use raid_attr for minimum stripe count in
btrfs_calc_avail_data_space
btrfs: lift bio_set_dev from bio allocation helpers
fs/btrfs/compression.c | 12 ++++++++----
fs/btrfs/extent-tree.c | 14 +++++++-------
fs/btrfs/extent_io.c | 23 ++++++++++++++---------
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/file.c | 6 +++---
fs/btrfs/super.c | 15 +++++++--------
6 files changed, 40 insertions(+), 32 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-18 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 18:00 David Sterba [this message]
2019-06-18 18:00 ` [PATCH 1/6] btrfs: use common helpers for eb leak messages David Sterba
2019-06-18 18:00 ` [PATCH 2/6] btrfs: use common helpers for extent IO state insertion messages David Sterba
2019-06-19 6:54 ` Nikolay Borisov
2019-06-19 11:50 ` David Sterba
2019-06-18 18:00 ` [PATCH 3/6] btrfs: drop default value assignments in enums David Sterba
2019-06-18 18:00 ` [PATCH 4/6] btrfs: use raid_attr to adjust minimal stripe size in btrfs_calc_avail_data_space David Sterba
2019-06-19 6:57 ` Nikolay Borisov
2019-06-18 18:00 ` [PATCH 5/6] btrfs: use raid_attr for minimum stripe count " David Sterba
2019-06-19 7:51 ` Nikolay Borisov
2019-06-19 12:09 ` David Sterba
2019-06-18 18:00 ` [PATCH 6/6] btrfs: lift bio_set_dev from bio allocation helpers David Sterba
2019-06-19 7:02 ` Nikolay Borisov
2019-06-19 12:03 ` 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.1560880630.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.