mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Adrian Bunk <bunk@stusta.de>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: drivers/w1/w1_int.c compile error with NET=n
Date: Tue, 19 Jul 2005 10:49:31 +0400	[thread overview]
Message-ID: <20050719104931.A22238@2ka.mipt.ru> (raw)
In-Reply-To: <20050719000549.GD5031@stusta.de>; from bunk@stusta.de on Tue, Jul 19, 2005 at 02:05:49AM +0200

On Tue, Jul 19, 2005 at 02:05:49AM +0200, Adrian Bunk (bunk@stusta.de) wrote:
> I'm seeing the following compile error in 2.6.13-rc3-mm1 (but it doesn't 
> seem to be specific to -mm) with CONFIG_NET=n:
> 
> <--  snip  -->
> 
> ...
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `w1_alloc_dev':
> w1_int.c:(.text+0x65d81f): undefined reference to `netlink_kernel_create'
> w1_int.c:(.text+0x65d881): undefined reference to `sock_release'
> drivers/built-in.o: In function `w1_free_dev':
> w1_int.c:(.text+0x65d8e9): undefined reference to `sock_release'
> make: *** [.tmp_vmlinux1] Error 1
> 
> <--  snip  -->
> 

Something changed...
Those functions were exported before even with NET disabled.
There is a NETLINK_DISABLE config option which guards message
sending, now it should guard socket creation too.

Thanks, Adrian, I will create a patch for it.

> 
> cu
> Adrian
> 
> -- 
> 
>        "Is there not promise of rain?" Ling Tan asked suddenly out
>         of the darkness. There had been need of rain for many days.
>        "Only a promise," Lao Er said.
>                                        Pearl S. Buck - Dragon Seed
> 

-- 
	Evgeniy Polyakov

      reply	other threads:[~2005-07-19  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  0:05 Adrian Bunk
2005-07-19  6:49 ` Evgeniy Polyakov [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=20050719104931.A22238@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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

all inboxes | Powered by JetHome®