From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for August 6 (8390 et al)
Date: Thu, 7 Aug 2008 09:20:07 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808070918510.17614@anakin> (raw)
In-Reply-To: <20080806172148.7fac5999.randy.dunlap@oracle.com>
On Wed, 6 Aug 2008, Randy Dunlap wrote:
> One randconfig ends with:
>
> drivers/built-in.o: In function `wd_probe1':
> wd.c:(.init.text+0x6179): undefined reference to `NS8390p_init'
> make[1]: *** [.tmp_vmlinux1] Error 1
drivers/net/Makefile has:
obj-$(CONFIG_WD80x3) += wd.o 8390.o
So either wd_probe1() should call NS8390_init(), or obj-$(CONFIG_WD80x3)
should link with 8390p.o. Don't know which is the appropriate change
here (my gut feeling says the latter).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-08-07 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 8:28 linux-next: Tree for August 6 Stephen Rothwell
2008-08-07 0:21 ` linux-next: Tree for August 6 (8390 et al) Randy Dunlap
2008-08-07 7:20 ` Geert Uytterhoeven [this message]
2008-08-07 9:29 ` Alan Cox
2008-08-11 9:11 ` [PATCH] net, wd.c: fix undefined reference to `NS8390p_init' Ingo Molnar
2008-08-11 9:47 ` Jeff Garzik
2008-08-11 11:11 ` Ingo Molnar
2008-08-11 20:51 ` David Miller
2008-08-07 0:29 ` [PATCH -next] Panasonic ACPI depends on INPUT Randy Dunlap
2008-08-11 11:25 ` Andi Kleen
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=Pine.LNX.4.64.0808070918510.17614@anakin \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).