linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] Cleanup volume.c of unused parameters/variables
Date: Thu, 13 Jul 2017 11:37:40 +0300	[thread overview]
Message-ID: <1499935063-24401-1-git-send-email-nborisov@suse.com> (raw)

Here are 3 cleanup patches which remove unused variables, parameters and 
kill a dummy function. 

Nikolay Borisov (3):
  btrfs: Remove unused variables
  btrfs: Remove unused parameters from volume.c functions
  btrfs: Remove find_raid56_stripe_len

 fs/btrfs/extent-tree.c |  6 ++----
 fs/btrfs/extent_io.c   |  2 +-
 fs/btrfs/volumes.c     | 44 ++++++++++----------------------------------
 fs/btrfs/volumes.h     |  3 +--
 4 files changed, 14 insertions(+), 41 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-07-13  8:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  8:37 Nikolay Borisov [this message]
2017-07-13  8:37 ` [PATCH 1/3] btrfs: Remove unused variables Nikolay Borisov
     [not found]   ` <1499935536-25223-1-git-send-email-nborisov@suse.com>
2017-07-14  2:08     ` [PATCH 3/3] btrfs: Remove find_raid56_stripe_len Qu Wenruo
2017-07-14  6:55       ` [PATCH v2] " Nikolay Borisov
2017-07-14  7:03         ` Qu Wenruo
2017-07-18 16:19         ` David Sterba
2017-07-14  2:21   ` [PATCH 1/3] btrfs: Remove unused variables Qu Wenruo
2017-07-18 15:54   ` David Sterba
2017-07-19  7:47     ` [PATCH v2] " Nikolay Borisov
2017-07-21 15:52       ` David Sterba
2017-07-13  8:37 ` [PATCH 2/3] btrfs: Remove unused parameters from volume.c functions Nikolay Borisov
2017-07-18 16:09   ` David Sterba
2017-07-19  7:48     ` [PATCH v2] " Nikolay Borisov
2017-07-21 16:00       ` David Sterba
2017-07-13  8:37 ` [PATCH 3/3] btrfs: Remove find_raid56_stripe_len 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=1499935063-24401-1-git-send-email-nborisov@suse.com \
    --to=nborisov@suse.com \
    --cc=dsterba@suse.cz \
    --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).