linux-kernel - [PATCH -next] dmar: fix build warnings when ACPI is not enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E820876.5090206@xenotime.net>
Date:	Tue, 27 Sep 2011 10:31:34 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Vinod Koul <vinod.koul@...el.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH -next] dmar: fix build warnings when ACPI is not enabled

From: Randy Dunlap <rdunlap@...otime.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@...otime.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)
 {
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/