From: Ralf Baechle <ralf@linux-mips.org>
To: Jim Gifford <maillist@jg555.com>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: Current Build Warning Message
Date: Tue, 15 Mar 2005 21:55:39 +0000 [thread overview]
Message-ID: <20050315215538.GJ6025@linux-mips.org> (raw)
In-Reply-To: <42375617.3020002@jg555.com>
On Tue, Mar 15, 2005 at 01:39:35PM -0800, Jim Gifford wrote:
> Date: Tue, 15 Mar 2005 13:39:35 -0800
> From: Jim Gifford <maillist@jg555.com>
> To: Linux MIPS List <linux-mips@linux-mips.org>
> Subject: Current Build Warning Message
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I just tried doing a current build on a 2.6.11 systems. I get the
> following warnings.
>
> *** Warning: "pci_iounmap" [drivers/net/tulip/tulip.ko] undefined!
> *** Warning: "pci_iomap" [drivers/net/tulip/tulip.ko] undefined!
>
> Any ideas on how to correct this?
Write pci_iounmap and pci_iomap :-)
(Recently an implementation was posted here but it's been broken as it
only did support a single PCI bus and will fail silently for additional
busses.)
Ralf
next prev parent reply other threads:[~2005-03-16 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 21:39 Current Build Warning Message Jim Gifford
2005-03-15 21:55 ` Ralf Baechle [this message]
[not found] ` <423EF440.9090902@jg555.com>
2005-03-21 16:33 ` Jim Gifford
2005-03-21 19:51 ` Jim Gifford
2005-03-21 20:00 ` Jim Gifford
2005-03-22 0:40 ` Atsushi Nemoto
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=20050315215538.GJ6025@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.com \
/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