From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Brian Norris <computersforpeace@gmail•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Mario Rugiero <mrugiero@gmail•com>
Subject: linux-next: build warning after merge of the l2-mtd tree
Date: Mon, 24 Jul 2017 11:48:36 +1000 [thread overview]
Message-ID: <20170724114836.08a7da64@canb.auug.org.au> (raw)
Hi Brian,
After merging the l2-mtd tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/mtd/mtdswap.c: In function 'mtdswap_add_debugfs':
drivers/mtd/mtdswap.c:1317:17: warning: unused variable 'dev' [-Wunused-variable]
struct device *dev = disk_to_dev(gd);
^
Introduced by commit
e8e3edb95ce6 ("mtd: create per-device and module-scope debugfs entries")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-07-24 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 1:48 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-23 1:32 linux-next: build warning after merge of the l2-mtd tree Stephen Rothwell
2017-06-23 4:56 ` Rafał Miłecki
2017-06-23 17:59 ` Brian Norris
2011-11-29 3:33 Stephen Rothwell
2011-11-29 9:54 ` Robert Jarzmik
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=20170724114836.08a7da64@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=computersforpeace@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mrugiero@gmail$(echo .)com \
/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