From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let W1 select NET
Date: Fri, 13 Aug 2004 14:31:35 +0400 [thread overview]
Message-ID: <1092393095.12729.424.camel@uganda> (raw)
In-Reply-To: <20040813101717.GS13377@fs.tum.de>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
On Fri, 2004-08-13 at 14:17, Adrian Bunk wrote:
> W1=y and Net=n fails with the following compile error:
>
> <-- snip -->
>
> ...
> LD .tmp_vmlinux1
> drivers/built-in.o(.text+0x5efa38): In function `w1_alloc_dev':
> : undefined reference to `netlink_kernel_create'
> drivers/built-in.o(.text+0x5efac1): In function `w1_alloc_dev':
> : undefined reference to `sock_release'
> drivers/built-in.o(.text+0x5efb31): In function `w1_free_dev':
> : undefined reference to `sock_release'
> drivers/built-in.o(.text+0x5f0014): In function `w1_netlink_send':
> : undefined reference to `alloc_skb'
> drivers/built-in.o(.text+0x5f00cd): In function `w1_netlink_send':
> : undefined reference to `netlink_broadcast'
> drivers/built-in.o(.text+0x5f0131): In function `w1_netlink_send':
> : undefined reference to `skb_over_panic'
> make: *** [.tmp_vmlinux1] Error 1
>
> <-- snip -->
>
>
> The patch below fixes this issue by letting W1 select NET.
Sure.
W1 requires netlink and thus CONFIG_NET.
Thank you.
I've applied your patch to my tree
and will send it to GregKH -> Andrew Morton.
>
> Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
>
> --- linux-2.6.8-rc4-mm1-full-3.4/drivers/w1/Kconfig.old 2004-08-13 12:00:05.000000000 +0200
> +++ linux-2.6.8-rc4-mm1-full-3.4/drivers/w1/Kconfig 2004-08-13 12:11:31.000000000 +0200
> @@ -2,6 +2,7 @@
>
> config W1
> tristate "Dallas's 1-wire support"
> + select NET
> ---help---
> Dallas's 1-wire bus is usefull to connect slow 1-pin devices
> such as iButtons and thermal sensors.
--
Evgeniy Polyakov ( s0mbre )
Crash is better than data corruption. -- Art Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-13 10:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:17 [2.6 patch] let W1 select NET Adrian Bunk
2004-08-13 10:31 ` Evgeniy Polyakov [this message]
2004-08-13 10:32 ` Roman Zippel
2004-08-13 10:46 ` Evgeniy Polyakov
2004-08-13 10:54 ` Roman Zippel
2004-08-13 11:01 ` Adrian Bunk
2004-08-13 11:26 ` Bernd Eckenfels
2004-08-13 12:11 ` Roman Zippel
2004-08-13 12:24 ` Adrian Bunk
2004-08-13 17:00 ` Randy.Dunlap
2004-08-15 17:13 ` Roman Zippel
2004-08-13 12:12 ` Russell King
2004-08-16 2:18 ` Miles Bader
2004-08-13 11:06 ` Evgeniy Polyakov
2004-08-13 10:54 ` Adrian Bunk
2004-08-13 11:06 ` Roman Zippel
2004-08-13 13:52 ` Cornelia Huck
2004-08-13 15:10 ` Evgeniy Polyakov
2004-08-13 15:45 ` Cornelia Huck
2004-08-13 17:12 ` Evgeniy Polyakov
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=1092393095.12729.424.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.