From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/4] Misc cleanups
Date: Wed, 27 Jun 2018 16:38:21 +0300 [thread overview]
Message-ID: <1530106705-27186-1-git-send-email-nborisov@suse.com> (raw)
Here are a couples of cleanups of things I observed while looking at the
extent_buffer management code.
Patch 1 rewrites a do {} while into a simple for() construct. This survived
xfstest + selftests
Patch 2 substitutes and outdated comment for a lockdep_assert_held call
Patch 3 rename the idiotic EXTENT_BUFFER_DUMMY to something more meaningful
Patch 4 removes some cargo-cult copied code when performing qgroup leaf scan
Nikolay Borisov (4):
btrfs: Refactor loop in btrfs_release_extent_buffer_page
btrfs: Document locking require via lockdep_assert_held
btrfs: Rename EXTENT_BUFFER_DUMMY to EXTENT_BUFFER_PRIVATE
btrfs: Remove unnecessary locking code in qgroup_rescan_leaf
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/extent_io.c | 26 +++++++++++---------------
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/qgroup.c | 7 +------
4 files changed, 14 insertions(+), 23 deletions(-)
--
2.7.4
next reply other threads:[~2018-06-27 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 13:38 Nikolay Borisov [this message]
2018-06-27 13:38 ` [PATCH 1/4] btrfs: Refactor loop in btrfs_release_extent_buffer_page Nikolay Borisov
2018-06-29 12:35 ` David Sterba
2018-07-02 10:03 ` Nikolay Borisov
2018-07-19 15:19 ` David Sterba
2018-06-27 13:38 ` [PATCH 2/4] btrfs: Document locking require via lockdep_assert_held Nikolay Borisov
2018-06-27 13:38 ` [PATCH 3/4] btrfs: Rename EXTENT_BUFFER_DUMMY to EXTENT_BUFFER_PRIVATE Nikolay Borisov
2018-06-29 12:46 ` David Sterba
2018-06-29 13:07 ` Qu Wenruo
2018-06-29 13:42 ` Nikolay Borisov
2018-07-19 15:40 ` David Sterba
2018-06-29 13:53 ` David Sterba
2018-06-27 13:38 ` [PATCH 4/4] btrfs: Remove unnecessary locking code in qgroup_rescan_leaf Nikolay Borisov
2018-07-02 13:32 ` Nikolay Borisov
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 20:00 [PATCH 0/4] Misc cleanups David Sterba
2018-04-11 8:21 Nikolay Borisov
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=1530106705-27186-1-git-send-email-nborisov@suse.com \
--to=nborisov@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.