linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Buesch <mb@bu3sch.de>, linux-wireless@vger.kernel.org
Subject: Re: superh allmodconfig
Date: Thu, 9 Aug 2007 08:13:44 +0900	[thread overview]
Message-ID: <20070808231344.GA22446@linux-sh.org> (raw)
In-Reply-To: <20070808160619.1b483888.akpm@linux-foundation.org>

On Wed, Aug 08, 2007 at 04:06:19PM -0700, Andrew Morton wrote:
> drivers/net/b44.c: In function `b44_sync_dma_desc_for_cpu':
> drivers/net/b44.c:159: error: implicit declaration of function `dma_sync_single_range_for_cpu'
> 
> This is actually an sh problem.  It hit sparc64 too but davem fixed
> it.  Seems that secveral architectures are lagging a bit in the PCI
> API area, and b44 is using things whcih other drivers are not.

I'll fix it up, thanks.

      reply	other threads:[~2007-08-08 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 23:06 superh allmodconfig Andrew Morton
2007-08-08 23:13 ` Paul Mundt [this message]

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=20070808231344.GA22446@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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).