All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: brudley@broadcom.com, henryp@broadcom.com, rvossen@broadcom.com,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: build failure after merge of the final tree (staging related)
Date: Fri, 10 Jun 2011 15:34:23 -0700	[thread overview]
Message-ID: <20110610223423.GB15868@kroah.com> (raw)
In-Reply-To: <20110610160938.cd01c408.sfr@canb.auug.org.au>

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@canb.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

  reply	other threads:[~2011-06-10 22:35 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  7:27 linux-next: build failure after merge of the final tree (staging related) Stephen Rothwell
2011-06-09 18:41 ` Greg KH
2011-06-09 19:22   ` Greg KH
2011-06-10  6:05     ` Stephen Rothwell
2011-06-10  6:09       ` Stephen Rothwell
2011-06-10 22:34         ` Greg KH [this message]
2011-06-15  4:21           ` Stephen Rothwell
2011-06-16 19:14             ` Greg KH
2011-06-23  0:35               ` Stephen Rothwell
2011-06-23 21:51                 ` Greg KH
2011-06-24  0:00                   ` Stephen Rothwell
2011-06-27 21:45                     ` Greg KH
2011-06-28  0:16                       ` Stephen Rothwell
2011-06-15 12:05       ` Geert Uytterhoeven
2011-06-15 12:05         ` Geert Uytterhoeven
2011-06-15 15:47         ` Greg KH
2011-06-15 15:47           ` linux-next: build failure after merge of the final tree (staging Greg KH
2011-06-15 14:35       ` [PATCH] arch/tile: remove useless set_fixmap_nocache() macro Chris Metcalf
2011-06-15 14:35       ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-09 19:52   ` linux-next: build failure after merge of the final tree (staging related) Henry Ptasinski
2011-06-09 20:19     ` Greg KH
2012-06-12  4:54 linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell
2012-06-12  4:54 ` Stephen Rothwell
2012-06-12 15:31 ` Bjorn Helgaas
2012-06-12 15:31   ` Bjorn Helgaas
2012-06-12 15:31   ` Bjorn Helgaas
2012-06-13  0:50   ` Stephen Rothwell
2012-06-13  0:50     ` Stephen Rothwell
2012-06-13 23:20     ` Bjorn Helgaas
2012-06-13 23:20       ` Bjorn Helgaas
2013-02-11  7:34 linux-next: build failure after merge of the final tree (acpi " Stephen Rothwell
2013-02-11  7:34 ` Stephen Rothwell
2013-02-11 18:22 ` Bjorn Helgaas
2013-02-11 18:22   ` Bjorn Helgaas
2013-02-11 23:23 ` Len Brown
2013-02-11 23:23   ` Len Brown
2013-02-12 17:35   ` Sam Ravnborg
2013-02-12 17:35     ` Sam Ravnborg
2013-02-12 18:01     ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Len Brown
2013-02-12 18:01       ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree r Len Brown
2013-02-12 18:03       ` Should SPARC use cpuidle? Len Brown
2013-02-12 18:03         ` Len Brown
2013-02-12 19:36         ` Sam Ravnborg
2013-02-12 19:36           ` Sam Ravnborg
2013-02-12 19:42       ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Sam Ravnborg
2013-02-12 19:42         ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tr Sam Ravnborg
2014-04-22  6:22 linux-next: build failure after merge of the audit tree Stephen Rothwell
2014-04-22  6:22 ` Stephen Rothwell
2014-04-22 15:56 ` Richard Guy Briggs
2014-04-22 15:56   ` Richard Guy Briggs
2014-04-22 16:32 ` Eric Paris
2014-04-22 16:32   ` Eric Paris
2014-04-22 21:27   ` Stephen Rothwell
2014-04-22 21:27     ` Stephen Rothwell
2017-11-30  3:46 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2017-11-30  3:46 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110610223423.GB15868@kroah.com \
    --to=greg@kroah.com \
    --cc=brudley@broadcom.com \
    --cc=henryp@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.