[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1159844100.2349.5.camel@entropy>
Date: Mon, 02 Oct 2006 19:55:00 -0700
From: Nicholas Miell <nmiell@...cast.net>
To: Adrian Bunk <bunk@...sta.de>
Cc: Judith Lebzelter <judith@...l.org>, linux-kernel@...r.kernel.org,
linuxppc-dev@...abs.org
Subject: Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on
i386
On Tue, 2006-10-03 at 03:58 +0200, Adrian Bunk wrote:
> On Mon, Oct 02, 2006 at 06:48:11PM -0700, Nicholas Miell wrote:
> > On Tue, 2006-10-03 at 03:22 +0200, Adrian Bunk wrote:
> > > On Tue, Oct 03, 2006 at 01:44:28AM +0200, Adrian Bunk wrote:
> > > > On Mon, Oct 02, 2006 at 02:49:54PM -0700, Judith Lebzelter wrote:
> > > >
> > > > > Hello:
> > > >
> > > > Hi Judith,
> > > >
> > > > > For the automated cross-compile builds at OSDL, powerpc 64-bit
> > > > > 'allmodconfig' is failing. The warnings/errors below appear in
> > > > > the 'modpost' stage of kernel compiles for 2.6.18 and -mm2 kernels.
> > > >
> > > > known for ages - the drivers need fixing.
> > > >
> > > > You might want to convince Andrew accepting my patch to make
> > > > virt_to_bus/bus_to_virt give compile warnings on i386 for making
> > > > people more aware of this problem...
> > > >...
> > >
> > > In case anyone is interested, the patch is below.
> > >
> > > cu
> > > Adrian
> > >
> >
> > Won't this also cause warnings for valid arch-specific usage (i.e. in
> > linux/arch/{i386,x86_64})?
>
> They aren't used under linux/arch/i386/ and my patch doesn't change x86_64.
Sorry, for some reason I thought isa_bus_to_virt and isa_virt_to_bus
were defined in terms of virt_to_bus/bus_to_virt instead of
virt_to_phys/phys_to_virt.
--
Nicholas Miell <nmiell@...cast.net>
-
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/
Powered by blists - more mailing lists