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>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: [PATCH -next] acpi: fix acpi_bus.h warnings when ACPI is not enabled
Date: Wed, 23 May 2012 09:14:21 -0700 [thread overview]
Message-ID: <4FBD0CDD.6010003@xenotime.net> (raw)
In-Reply-To: <20120523170740.ae058d8d5468d471eb948c39@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix header file warnings when CONFIG_ACPI is not enabled:
include/acpi/acpi_bus.h:443:42: warning: 'struct acpi_bus_type' declared inside parameter list
include/acpi/acpi_bus.h:443:42: warning: its scope is only this definition or declaration, which is probably not what you want
include/acpi/acpi_bus.h:444:44: warning: 'struct acpi_bus_type' declared inside parameter list
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
include/acpi/acpi_bus.h | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20120523.orig/include/acpi/acpi_bus.h
+++ linux-next-20120523/include/acpi/acpi_bus.h
@@ -440,6 +440,8 @@ static inline int acpi_pm_device_sleep_w
#else /* CONFIG_ACPI */
+struct acpi_bus_type;
+
static int register_acpi_bus_type(struct acpi_bus_type *bus) { return 0; }
static int unregister_acpi_bus_type(struct acpi_bus_type *bus) { return 0; }
next prev parent reply other threads:[~2012-05-23 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 7:07 linux-next: Tree for May 23 Stephen Rothwell
2012-05-23 8:10 ` Nicholas A. Bellinger
2012-05-23 15:58 ` linux-next: Tree for May 23 (uml) Randy Dunlap
2012-05-23 18:19 ` Al Viro
2012-05-23 19:37 ` Al Viro
2012-05-23 23:13 ` Stephen Rothwell
2012-05-23 23:47 ` Al Viro
2012-05-23 20:51 ` Geert Uytterhoeven
2012-05-23 16:14 ` Randy Dunlap [this message]
2012-06-04 4:32 ` [PATCH -next] acpi: fix acpi_bus.h warnings when ACPI is not enabled Len Brown
2012-06-04 14:42 ` 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=4FBD0CDD.6010003@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).