From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] VIA_VELOCITY must depend on INET
Date: Wed, 20 Jul 2005 12:26:26 +0100 [thread overview]
Message-ID: <1121858786.11024.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20050719135523.GF5031@stusta.de>
On Maw, 2005-07-19 at 15:55 +0200, Adrian Bunk wrote:
> VIA_VELOCITY=y and INET=n results in the following compile error:
>
> <-- snip -->
>
> ...
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `velocity_register_notifier':
> via-velocity.c:(.text+0x3462c6): undefined reference to `register_inetaddr_notifier'
> drivers/built-in.o: In function `velocity_unregister_notifier':
> via-velocity.c:(.text+0x3462d6): undefined reference to `unregister_inetaddr_notifier'
> make: *** [.tmp_vmlinux1] Error 1
Alternatively you could drop those functions when CONFIG_INET is n as
they are only used for wake on arp
prev parent reply other threads:[~2005-07-20 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 13:55 [2.6 patch] VIA_VELOCITY must depend on INET Adrian Bunk
2005-07-20 11:26 ` Alan Cox [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=1121858786.11024.25.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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).