[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1229034191.8766.63.camel@bodhitayantram.eng.vmware.com>
Date: Thu, 11 Dec 2008 14:23:11 -0800
From: Zachary Amsden <zach@...are.com>
To: Greg KH <gregkh@...e.de>
Cc: Yinghai Lu <yinghai@...nel.org>, Huang Ying <ying.huang@...el.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
"norman@...backs.co.uk" <norman@...backs.co.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alok Kataria <alokkataria1@...il.com>,
"bruno.premont@...tena.lu" <bruno.premont@...tena.lu>,
"xl@...igned.net" <xl@...igned.net>,
"dsd@...too.org" <dsd@...too.org>
Subject: Re: [PATCH] Fix VMI crash on boot in 2.6.27, 2.6.28 kernels
On Wed, 2008-12-10 at 19:31 -0800, Greg KH wrote:
> > +#ifdef CONFIG_VMI
> > + /* VMI may relocate the fixmap; do this before touching ioremap area */
> > + vmi_init();
> > +#endif
>
> Shouldn't the #ifdef not be needed here if the .h files are set up
> properly for the vmi_init prototype? Please try to keep them out of .c
> files wherever possible.
Yes, they should. Judging by setup.c though, you would think the
opposite... in any case I fixed it. Please apply - and yes, I tested
compile both ways.
View attachment "x86-vmi-boot-ioremap-fix-take-3.patch" of type "text/x-patch" (3077 bytes)
Powered by blists - more mailing lists