From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Nikolay Borisov <nborisov@suse.com>
Subject: linux-next: build warning after merge of the btrfs tree
Date: Tue, 25 Aug 2020 10:45:07 +1000 [thread overview]
Message-ID: <20200825104507.4c79c433@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Hi all,
After merging the btrfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
fs/btrfs/volumes.c: In function 'btrfs_rm_dev_replace_free_srcdev':
fs/btrfs/volumes.c:2217:24: warning: unused variable 'fs_info' [-Wunused-variable]
2217 | struct btrfs_fs_info *fs_info = srcdev->fs_info;
| ^~~~~~~
Introduced by commits
2a6fac3ea9a1 ("btrfs: move btrfs_scratch_superblocks into btrfs_dev_replace_finishing")
438ac6dd65ef ("btrfs: switch seed device to list api")
merged in commit
76e6c55d5432 ("Merge branch 'ext/nikbor/seed-cleanups-v2' into for-next-next-v5.9-20200824")
which should have removed the declaration.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-08-25 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 0:45 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 1:03 linux-next: build warning after merge of the btrfs tree Stephen Rothwell
2021-01-26 23:18 Stephen Rothwell
2021-01-27 19:46 ` David Sterba
2020-02-23 22:57 Stephen Rothwell
2020-02-24 14:34 ` David Sterba
2020-02-11 22:10 Stephen Rothwell
2020-02-12 16:03 ` David Sterba
2020-02-20 22:32 ` Stephen Rothwell
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=20200825104507.4c79c433@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nborisov@suse.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