From: Eric Biggers <ebiggers@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Theodore Ts'o <tytso@mit.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the ext4 tree
Date: Thu, 19 May 2022 23:35:20 -0700 [thread overview]
Message-ID: <Yoc2qBFeU1UoNRpV@sol.localdomain> (raw)
In-Reply-To: <20220520110313.48a824c4@canb.auug.org.au>
On Fri, May 20, 2022 at 11:03:13AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the ext4 tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/ext4/super.c: In function 'ext4_check_test_dummy_encryption':
> fs/ext4/super.c:2677:36: warning: unused variable 'sbi' [-Wunused-variable]
> 2677 | const struct ext4_sb_info *sbi = EXT4_SB(sb);
> | ^~~
>
> Introduced by commit
>
> 0df27ddf69f3 ("ext4: only allow test_dummy_encryption when supported")
>
The kernel test robot beat you to it! This warning happens when
!CONFIG_FS_ENCRYPTION. v4 of the patch fixes this
(https://lore.kernel.org/r/20220519204437.61645-1-ebiggers@kernel.org).
- Eric
next prev parent reply other threads:[~2022-05-20 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 1:03 linux-next: build warning after merge of the ext4 tree Stephen Rothwell
2022-05-20 6:35 ` Eric Biggers [this message]
2022-05-20 12:54 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 8:22 Stephen Rothwell
2024-07-30 10:06 ` Stephen Rothwell
2021-07-05 23:46 Stephen Rothwell
2018-10-09 23:11 Stephen Rothwell
2016-01-05 6:01 Stephen Rothwell
2011-01-10 1:10 Stephen Rothwell
2010-08-07 2:45 Stephen Rothwell
2010-08-07 6:47 ` Ted Ts'o
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=Yoc2qBFeU1UoNRpV@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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).