From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Qu Wenruo <wqu@suse.com>
Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree
Date: Mon, 28 Jan 2019 17:53:42 +0100 [thread overview]
Message-ID: <20190128165342.GH2900@suse.cz> (raw)
In-Reply-To: <20190124095338.523fc3a3@canb.auug.org.au>
On Thu, Jan 24, 2019 at 09:53:38AM +1100, Stephen Rothwell wrote:
> Hi David,
>
> After merging the btrfs-kdave tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/btrfs/relocation.c: In function 'insert_dirty_subv':
> fs/btrfs/relocation.c:2138:6: warning: unused variable 'root_objectid' [-Wunused-variable]
> u64 root_objectid = root->root_key.objectid;
> ^~~~~~~~~~~~~
>
> Introduced by commit
>
> 7b837199c581 ("btrfs: relocation: Delay reloc tree deletion after merge_reloc_roots()")
>
> Presumably the ASSERT is compiled out in this configuration.
Agreed, thanks for the report. I'll drop the temporary variable.
next prev parent reply other threads:[~2019-01-28 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 22:53 linux-next: build warning after merge of the btrfs-kdave tree Stephen Rothwell
2019-01-28 16:53 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-03 0:21 Stephen Rothwell
2019-05-03 13:37 ` David Sterba
2018-11-26 0:06 Stephen Rothwell
2018-11-26 7:56 ` Christoph Hellwig
2017-12-19 22:20 Stephen Rothwell
2017-12-20 0:12 ` Qu Wenruo
2017-12-21 16:49 ` David Sterba
2017-12-22 0:32 ` Qu Wenruo
2017-05-17 23:41 Stephen Rothwell
2017-05-18 12:50 ` David Sterba
2017-05-25 1:31 ` Stephen Rothwell
2016-11-28 0:02 Stephen Rothwell
2016-12-06 22:38 ` Stephen Rothwell
2016-12-14 15:19 ` 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=20190128165342.GH2900@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wqu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.