From: Nikolay Borisov <nborisov@suse.com>
To: Johannes Thumshirn <jthumshirn@suse.de>, David Sterba <dsterba@suse.com>
Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/6] btrfs: fix compiler warning with make W=1
Date: Wed, 14 Nov 2018 15:50:15 +0200 [thread overview]
Message-ID: <683aa762-c668-d19c-2f7f-7f62a3f2adc6@suse.com> (raw)
In-Reply-To: <20181114133520.16069-1-jthumshirn@suse.de>
On 14.11.18 г. 15:35 ч., Johannes Thumshirn wrote:
> This patchset fixes most of the compiler warnings encountered when building
> btrfs with make W=1.
>
> There are two more compiler warnings left in raid56.c:
> CC [M] fs/btrfs/raid56.o
> fs/btrfs/raid56.c: In function ‘finish_rmw’:
> fs/btrfs/raid56.c:1185:6: warning: variable ‘p_stripe’ set but not used [-Wunused-but-set-variable]
> int p_stripe = -1;
> ^
> fs/btrfs/raid56.c: In function ‘finish_parity_scrub’:
> fs/btrfs/raid56.c:2343:6: warning: variable ‘p_stripe’ set but not used [-Wunused-but-set-variable]
> int p_stripe = -1;
> ^
> but I'm currently unsure how an appropriate fix would look like. As far as I
> can tell these variables have always been unused since they have been
> introduced.
>
> There are still warnings left emitted by kernel-doc but these are subject to
> another patchset, this one only addresses the warnings generated by gcc.
>
> Johannes Thumshirn (6):
> btrfs: remove unused drop_on_err in btrfs_mkdir()
> btrfs: remove set but not used variable err in btrfs_add_link
> btrfs: remove unused function btrfs_sysfs_feature_update()
> btrfs: remove unused variable tree in bio_readpage_error()
> btrfs: remove unused variable tree in end_compressed_bio_write()
> btrfs: unconditionally provide function prototypes from
> free-space-tree.h
>
> fs/btrfs/compression.c | 2 --
> fs/btrfs/extent_io.c | 3 ---
> fs/btrfs/free-space-tree.h | 2 --
> fs/btrfs/inode.c | 16 ++++++----------
> fs/btrfs/sysfs.c | 33 ---------------------------------
> fs/btrfs/sysfs.h | 2 --
> 6 files changed, 6 insertions(+), 52 deletions(-)
For the whole series:
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
However, I have some comments for some of the patches.
>
next prev parent reply other threads:[~2018-11-14 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:35 [PATCH 0/6] btrfs: fix compiler warning with make W=1 Johannes Thumshirn
2018-11-14 13:35 ` [PATCH 1/6] btrfs: remove unused drop_on_err in btrfs_mkdir() Johannes Thumshirn
2018-11-14 19:29 ` Omar Sandoval
2018-11-14 13:35 ` [PATCH 2/6] btrfs: remove set but not used variable err in btrfs_add_link Johannes Thumshirn
2018-11-14 13:51 ` Nikolay Borisov
2018-11-14 13:35 ` [PATCH 3/6] btrfs: remove unused function btrfs_sysfs_feature_update() Johannes Thumshirn
2018-11-14 19:31 ` Omar Sandoval
2018-11-14 13:35 ` [PATCH 4/6] btrfs: remove unused variable tree in bio_readpage_error() Johannes Thumshirn
2018-11-14 19:32 ` Omar Sandoval
2018-11-14 13:35 ` [PATCH 5/6] btrfs: remove unused variable tree in end_compressed_bio_write() Johannes Thumshirn
2018-11-14 19:33 ` Omar Sandoval
2018-11-14 21:04 ` David Sterba
2018-11-15 8:00 ` Johannes Thumshirn
2018-11-14 13:35 ` [PATCH 6/6] btrfs: unconditionally provide function prototypes from free-space-tree.h Johannes Thumshirn
2018-11-14 13:52 ` Nikolay Borisov
2018-11-14 13:54 ` Johannes Thumshirn
2018-11-14 19:53 ` David Sterba
2018-11-14 21:05 ` Nikolay Borisov
2018-11-15 0:09 ` David Sterba
2018-11-14 13:50 ` Nikolay Borisov [this message]
2018-11-15 1:30 ` [PATCH 0/6] btrfs: fix compiler warning with make W=1 Qu Wenruo
2018-11-15 10:17 ` 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=683aa762-c668-d19c-2f7f-7f62a3f2adc6@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=jthumshirn@suse.de \
--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).