From: Jeff Garzik <jeff@garzik.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, netdev@vger.kernel.org
Subject: Re: [NET] au1000_eth: Fix warnings.
Date: Wed, 27 Jun 2007 02:33:19 -0400 [thread overview]
Message-ID: <468204AF.9050606@garzik.org> (raw)
In-Reply-To: <20070624135953.GA16754@linux-mips.org>
Ralf Baechle wrote:
> Fixed by including <linux/dma-mapping.h>:
>
> CC drivers/net/au1000_eth.o
> drivers/net/au1000_eth.c: In function 'au1000_probe':
> drivers/net/au1000_eth.c:661: warning: implicit declaration of function 'dma_alloc_noncoherent'
> drivers/net/au1000_eth.c:802: warning: implicit declaration of function 'dma_free_noncoherent'
>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
applied to #upstream-fixes
prev parent reply other threads:[~2007-06-27 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 13:59 [NET] au1000_eth: Fix warnings Ralf Baechle
2007-06-25 23:02 ` Andrew Morton
2007-06-26 11:42 ` Ralf Baechle
2007-06-27 6:33 ` Jeff Garzik [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=468204AF.9050606@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).