From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: linux-next: build warning after merge of the regulator tree
Date: Wed, 7 Oct 2015 13:45:03 +1100 [thread overview]
Message-ID: <20151007134503.48dd5084@canb.auug.org.au> (raw)
Hi all,
After merging the regulator tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/regulator/core.c: At top level:
drivers/regulator/core.c:139:13: warning: 'regulator_lock_supply' defined but not used [-Wunused-function]
static void regulator_lock_supply(struct regulator_dev *rdev)
^
drivers/regulator/core.c:159:13: warning: 'regulator_unlock_supply' defined but not used [-Wunused-function]
static void regulator_unlock_supply(struct regulator_dev *rdev)
^
Introduced by commit
9f01cd4a915e ("regulator: core: introduce function to lock regulators and its supplies")
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
next reply other threads:[~2015-10-07 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 2:45 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-18 3:43 linux-next: build warning after merge of the regulator tree Stephen Rothwell
2016-04-18 9:15 ` Mark Brown
2018-10-02 3:07 Stephen Rothwell
2018-10-02 6:16 ` Matti Vaittinen
2018-10-02 6:25 ` Stephen Rothwell
2018-10-02 6:43 ` Matti Vaittinen
2018-10-02 13:02 ` Mark Brown
2020-01-10 2:41 Stephen Rothwell
2024-10-23 4:51 Stephen Rothwell
2024-10-23 4:52 Stephen Rothwell
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=20151007134503.48dd5084@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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