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>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH -next] dmar: fix build warnings when ACPI is not enabled
Date: Tue, 27 Sep 2011 10:31:34 -0700 [thread overview]
Message-ID: <4E820876.5090206@xenotime.net> (raw)
In-Reply-To: <20110926172348.be01ff9a1c16267ffd000d2a@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix build warnings when CONFIG_ACPI is not enabled:
include/linux/dmar.h:248:46: warning: 'struct acpi_dmar_header' declared inside parameter list
include/linux/dmar.h:248:46: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/dmar.h:252:46: warning: 'struct acpi_dmar_header' declared inside parameter list
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
include/linux/dmar.h | 2 ++
1 file changed, 2 insertions(+)
--- next-2011-0927.orig/include/linux/dmar.h
+++ next-2011-0927/include/linux/dmar.h
@@ -244,6 +244,8 @@ extern int dmar_parse_dev_scope(void *st
struct pci_dev ***devices, u16 segment);
extern int intel_iommu_init(void);
#else /* !CONFIG_INTEL_IOMMU: */
+struct acpi_dmar_header;
+
static inline int intel_iommu_init(void) { return -ENODEV; }
static inline int dmar_parse_one_rmrr(struct acpi_dmar_header *header)
{
prev parent reply other threads:[~2011-09-27 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:23 linux-next: Tree for Sept 26 Stephen Rothwell
2011-09-26 16:52 ` linux-next: Tree for Sept 26 (xen) Randy Dunlap
2011-09-26 17:18 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-09-26 17:10 ` linux-next: Tree for Sept 26 (olpc) Randy Dunlap
2011-09-26 17:31 ` linux-next: Tree for Sept 26 (block/mtip32xx) Randy Dunlap
2011-09-27 17:00 ` [PATCH -next] x86: perf_event_amd.c needs <asm/apicdef.h> Randy Dunlap
2011-09-28 6:58 ` Ingo Molnar
2011-09-27 17:31 ` Randy Dunlap [this message]
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=4E820876.5090206@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vinod.koul@intel.com \
/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