From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] Btrfs, remove unused structure members
Date: Tue, 16 May 2017 19:17:25 +0200 [thread overview]
Message-ID: <cover.1494954874.git.dsterba@suse.com> (raw)
With some help of coccinelle and coccigrep I found a few stucture members that
are completely unused, we can remove them and reduce structure sizes.
David Sterba (4):
btrfs: remove unused member err from reada_extent
btrfs: remove unused member list from async_submit_bio
btrfs: remove unused members dir_path from recorded_ref
btrfs: remove unused member list from btrfs_end_io_wq
fs/btrfs/disk-io.c | 2 --
fs/btrfs/reada.c | 1 -
fs/btrfs/send.c | 8 --------
3 files changed, 11 deletions(-)
--
2.12.0
next reply other threads:[~2017-05-16 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:17 David Sterba [this message]
2017-05-16 17:17 ` [PATCH 1/4] btrfs: remove unused member err from reada_extent David Sterba
2017-05-16 17:17 ` [PATCH 2/4] btrfs: remove unused member list from async_submit_bio David Sterba
2017-05-16 17:17 ` [PATCH 3/4] btrfs: remove unused members dir_path from recorded_ref David Sterba
2017-05-16 17:17 ` [PATCH 4/4] btrfs: remove unused member list from btrfs_end_io_wq 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.1494954874.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 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).