netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Meelis Roos <mroos@linux.ee>
Cc: netdev@vger.kernel.org
Subject: Re: b44 compile error on !PCI
Date: Thu, 2 Aug 2007 19:17:45 +0200	[thread overview]
Message-ID: <200708021917.45876.mb@bu3sch.de> (raw)
In-Reply-To: <Pine.SOC.4.64.0708021943510.7589@math.ut.ee>

On Thursday 02 August 2007, Meelis Roos wrote:
> Tryng to compile todays git on SBus-only Sparc64 (Ultra 1), no PCI. b44 
> is selectable but fails to compile:
> 
>   CC [M]  drivers/net/b44.o
> drivers/net/b44.c: In function 'b44_sync_dma_desc_for_device':
> drivers/net/b44.c:134: error: implicit declaration of function 'dma_sync_single_range_for_device'
> drivers/net/b44.c: In function 'b44_sync_dma_desc_for_cpu':
> drivers/net/b44.c:144: error: implicit declaration of function 'dma_sync_single_range_for_cpu'

Are you sure this is related to !PCI ?
If I grep include/asm-sparc64/dma-mapping.h I don't
find dma_sync_single_range_for_*
So I'd rather call this a bug in the arch code of sparc64.

  reply	other threads:[~2007-08-02 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 16:45 b44 compile error on !PCI Meelis Roos
2007-08-02 17:17 ` Michael Buesch [this message]
2007-08-05 10:03   ` Meelis Roos

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=200708021917.45876.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=mroos@linux.ee \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).