From: David Sterba <dsterba@suse.cz>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] btrfs: remove set but not used variable 'num_pages'
Date: Fri, 04 Jan 2019 15:51:17 +0000 [thread overview]
Message-ID: <20190104155117.GS23615@twin.jikos.cz> (raw)
In-Reply-To: <1544855467-154115-1-git-send-email-yuehaibing@huawei.com>
On Sat, Dec 15, 2018 at 06:31:07AM +0000, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> fs/btrfs/ioctl.c: In function 'btrfs_extent_same':
> fs/btrfs/ioctl.c:3260:6: warning:
> variable 'num_pages' set but not used [-Wunused-but-set-variable]
>
> It not used any more since commit 9ee8234e6220 ("Btrfs: use
> generic_remap_file_range_prep() for cloning and deduplication")
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Added to patch queue, thanks.
next prev parent reply other threads:[~2019-01-04 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 2:14 [PATCH -next] btrfs: remove set but not used variable 'tree' YueHaibing
2018-11-08 6:53 ` Nikolay Borisov
2018-11-08 12:11 ` David Sterba
2018-12-15 6:31 ` [PATCH -next] btrfs: remove set but not used variable 'num_pages' YueHaibing
2019-01-04 15:51 ` David Sterba [this message]
2019-03-27 3:20 ` [PATCH -next] btrfs: remove set but not used variable 'fs_devices' YueHaibing
2019-03-28 14:27 ` David Sterba
2019-04-18 6:43 ` [PATCH -next] btrfs: Remove set but not used variable 'fs_info' YueHaibing
2019-04-18 6:37 ` Nikolay Borisov
2019-04-18 7:34 ` YueHaibing
2019-04-18 13:43 ` 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=20190104155117.GS23615@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=yuehaibing@huawei.com \
/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