From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Mark Brown <broonie@opensource•wolfsonmicro.com>,
Andrew Morton <akpm@linux-foundation•org>
Subject: [PATCH -next] regmap: add structs to fix build warnings when REGMAP is not enabled
Date: Fri, 09 Mar 2012 11:31:57 -0800 [thread overview]
Message-ID: <4F5A5AAD.1000105@xenotime.net> (raw)
In-Reply-To: <20120309191101.8634973f7d9988c602143f7c@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime•net>
Fix build warnings when CONFIG_REGMAP is not enabled by providing
struct forward references.
CC [M] sound/soc/soc-core.o
In file included from include/sound/soc.h:22:0,
from sound/soc/soc-core.c:41:
include/linux/regmap.h:230:11: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:230:11: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/regmap.h:237:8: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:244:9: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:251:10: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:258:7: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:265:8: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:272:10: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:281:9: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:287:47: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:293:40: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:300:12: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:306:47: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:311:49: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:316:47: warning: 'struct regmap' declared inside parameter list
include/linux/regmap.h:323:6: warning: 'struct reg_default' declared inside parameter list
include/linux/regmap.h:323:6: warning: 'struct regmap' declared inside parameter list
Signed-off-by: Randy Dunlap <rdunlap@xenotime•net>
Cc: Mark Brown <broonie@opensource•wolfsonmicro.com>
---
include/linux/regmap.h | 3 +++
1 file changed, 3 insertions(+)
--- linux-next-20120308.orig/include/linux/regmap.h
+++ linux-next-20120308/include/linux/regmap.h
@@ -226,6 +226,9 @@ int regmap_irq_chip_get_base(struct regm
* REGMAP.
*/
+struct regmap;
+struct reg_default;
+
static inline int regmap_write(struct regmap *map, unsigned int reg,
unsigned int val)
{
next prev parent reply other threads:[~2012-03-09 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 8:11 linux-next: Tree for Mar 9 Stephen Rothwell
2012-03-09 19:31 ` Randy Dunlap [this message]
2012-03-11 11:57 ` [PATCH -next] regmap: add structs to fix build warnings when REGMAP is not enabled Mark Brown
2012-03-09 20:30 ` linux-next: Tree for Mar 9 (netfilter) Randy Dunlap
2012-03-10 11:21 ` Pablo Neira Ayuso
2012-03-10 16:45 ` Randy Dunlap
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=4F5A5AAD.1000105@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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