public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Ts'o <tytso@mit•edu>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build warning after merge of the ext4 tree
Date: Wed, 10 Oct 2018 10:11:28 +1100	[thread overview]
Message-ID: <20181010101128.2b151332@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

Hi Theodore,

After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

fs/ext4/super.c: In function 'parse_options':
fs/ext4/super.c:1976:26: warning: unused variable 'grp_qf_name' [-Wunused-variable]
  char *p, *usr_qf_name, *grp_qf_name;
                          ^~~~~~~~~~~
fs/ext4/super.c:1976:12: warning: unused variable 'usr_qf_name' [-Wunused-variable]
  char *p, *usr_qf_name, *grp_qf_name;
            ^~~~~~~~~~~

Introduced by commit

  20cefcdc2040 ("ext4: fix use-after-free race in ext4_remount()'s error path")

# CONFIG_QUOTA is not set

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-10-09 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 23:11 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-10  8:22 linux-next: build warning after merge of the ext4 tree Stephen Rothwell
2024-07-30 10:06 ` Stephen Rothwell
2022-05-20  1:03 Stephen Rothwell
2022-05-20  6:35 ` Eric Biggers
2022-05-20 12:54 ` Stephen Rothwell
2021-07-05 23:46 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=20181010101128.2b151332@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tytso@mit$(echo .)edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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