From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.27-rc1]: fix NE2000 linkage error
Date: Wed, 30 Jul 2008 17:15:22 -0400 [thread overview]
Message-ID: <4890D9EA.5080401@garzik.org> (raw)
In-Reply-To: <200807301144.m6UBitOG022822@harpo.it.uu.se>
Mikael Pettersson wrote:
> Trying to build with CONFIG_NE2000=m fails with:
>
> scripts/mod/modpost -o /tmp/tmp/linux-2.6.27-rc1/Module.symvers -S -s
> ERROR: "NS8390_init" [drivers/net/ne.ko] undefined!
>
> This is because the split of 8390 into pausing and non-pausing
> versions was incompletely propagated to ne.c. This fixes it.
>
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
actually, I take that back, I still needed a bit of this. thanks
prev parent reply other threads:[~2008-07-30 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 11:44 [PATCH 2.6.27-rc1]: fix NE2000 linkage error Mikael Pettersson
2008-07-30 14:04 ` Alan Cox
2008-07-30 17:55 ` Jeff Garzik
2008-07-30 21:15 ` 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=4890D9EA.5080401@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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).