From: kernel test robot <lkp@intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: oe-kbuild-all@lists.linux.dev, linux-ext4@vger.kernel.org
Subject: [tytso-ext4:pu 17/50] fs/ext4/super-test.c:219:6: warning: unused variable 'i'
Date: Thu, 12 Nov 2026 08:18:48 +0100 [thread overview]
Message-ID: <202611120832.HRTiXytu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git pu
head: 246d715a48c25a74ac372dda5e10d8f69f89b50a
commit: 1cec1055be7fc2b602f1cde94d772ec822ad6d74 [17/50] ext4: add KUnit tests for fs/ext4/super.c
config: parisc-randconfig-2001-20261112 (https://download.01.org/0day-ci/archive/20261112/202611120832.HRTiXytu-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261112/202611120832.HRTiXytu-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202611120832.HRTiXytu-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/ext4/super-test.c: In function 'super_test_cleanup':
>> fs/ext4/super-test.c:219:6: warning: unused variable 'i' [-Wunused-variable]
219 | int i;
| ^
vim +/i +219 fs/ext4/super-test.c
216
217 static void super_test_cleanup(struct super_test_ctx *ctx)
218 {
> 219 int i;
220
221 active_super_test = NULL;
222 ctx->sbi.s_journal = NULL;
223
224 if (ctx->journal_inode) {
225 iput(ctx->journal_inode);
226 ctx->journal_inode = NULL;
227 }
228
229 ext4_flex_groups_free_test(&ctx->sbi);
230
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-12 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202611120832.HRTiXytu-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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