[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110610223423.GB15868@kroah.com>
Date: Fri, 10 Jun 2011 15:34:23 -0700
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: brudley@...adcom.com, henryp@...adcom.com, rvossen@...adcom.com,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: build failure after merge of the final tree (staging
related)
On Fri, Jun 10, 2011 at 04:09:38PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Fri, 10 Jun 2011 16:05:48 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > No, I still get these:
> >
> > In file included from drivers/staging/comedi/drivers/addi_apci_035.c:7:0:
> > drivers/staging/comedi/drivers/addi-data/addi_common.c: In function 'i_ADDI_Attach':
> > drivers/staging/comedi/drivers/addi-data/addi_common.c:2765:7: error: implicit declaration of function 'virt_to_bus'
> >
> > virt_to_bus is only defined for 32 bit powerpc (not 64 bit) (and maybe
> > not at all on some architectures e.g. sparc).
> >
> > From Documentation/DMA-API-HOWTO.txt:
> > "All drivers should be using these interfaces with no exceptions. It
> > is planned to completely remove virt_to_bus() and bus_to_virt() as
> > they are entirely deprecated. Some ports already do not provide these
> > as it is impossible to correctly support them."
>
> Drivers that use virt_to_bus should Kconfig depend on VIRT_TO_BUS.
Ah, I missed that, sorry. I'll go make that change as well.
greg k-h
--
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