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,
Tuomas Tynkkynen <ttynkkynen@nvidia•com>
Subject: linux-next: build warnings after merge of the regulator tree
Date: Mon, 28 Jul 2014 20:32:33 +1000 [thread overview]
Message-ID: <20140728203233.26341abf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Hi all,
After merging the regulator tree, today's linux-next build (i386
defconfig among others) produced these warnings:
In file included from include/linux/regulator/machine.h:18:0,
from drivers/acpi/bus.c:36:
include/linux/regulator/consumer.h:468:23: warning: 'regulator_get_regmap' defined but not used [-Wunused-function]
static struct regmap *regulator_get_regmap(struct regulator *regulator)
^
include/linux/regulator/consumer.h:473:12: warning: 'regulator_get_hardware_vsel_register' defined but not used [-Wunused-function]
static int regulator_get_hardware_vsel_register(struct regulator *regulator,
^
include/linux/regulator/consumer.h:480:12: warning: 'regulator_list_hardware_vsel' defined but not used [-Wunused-function]
static int regulator_list_hardware_vsel(struct regulator *regulator,
^
And more like that.
Introduced by commit 04eca28cde52 ("regulator: Add helpers for
low-level register access"). Missing "static inline"s ... I suspect
this is becoming more common due to the lack of "extern"s in our header
files now. :-(
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-07-28 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 10:32 Stephen Rothwell [this message]
2014-07-28 13:49 ` linux-next: build warnings after merge of the regulator tree Mark Brown
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=20140728203233.26341abf@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ttynkkynen@nvidia$(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