clean up aperture_64.c
- From: Pavel Machek <pavel@xxxxxx>
- Date: Thu, 13 Mar 2008 11:03:58 +0100
Initializing to zero is generally bad idea, I hope it is right for
__init data, too.
Signed-off-by: Pavel Machek <pavel@xxxxxxx>
diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_64.c
index 608152a..88747f3 100644
--- a/arch/x86/kernel/aperture_64.c
+++ b/arch/x86/kernel/aperture_64.c
@@ -26,11 +27,11 @@ #include <asm/dma.h>
#include <asm/k8.h>
int gart_iommu_aperture;
-int gart_iommu_aperture_disabled __initdata = 0;
-int gart_iommu_aperture_allowed __initdata = 0;
+int gart_iommu_aperture_disabled __initdata;
+int gart_iommu_aperture_allowed __initdata;
int fallback_aper_order __initdata = 1; /* 64MB */
-int fallback_aper_force __initdata = 0;
+int fallback_aper_force __initdata;
int fix_aperture __initdata = 1;
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: clean up aperture_64.c
- From: Ingo Molnar
- Re: clean up aperture_64.c
- Prev by Date: Re: [PATCH 3/3] PM: make wakeup flags available whenever CONFIG_PM is set
- Next by Date: fix aperture vs. suspend problem
- Previous by thread: document memmap option better and help people with bad memory
- Next by thread: Re: clean up aperture_64.c
- Index(es):
Relevant Pages
|
