public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Maksim Krasnyanskiy <maxk@qualcomm.com>
Subject: Re: [PATCH] Make it possible to compile in the Bluetooth subsystem
Date: 07 Oct 2002 23:24:19 +0200	[thread overview]
Message-ID: <1034025872.861.81.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.33.0210071347470.10749-100000@penguin.transmeta.com>

On Mon, 2002-10-07 at 22:49, Linus Torvalds wrote:
> 
> On Mon, 7 Oct 2002, Marcel Holtmann wrote:
> > 
> > ChangeSet@1.709, 2002-10-07 22:08:56+02:00, marcel@holtmann.org
> >   Make it possible to compile in the Bluetooth subsystem
> 
> Looks good, but you should _not_ remove the "static". Please keep the init
> functions static, they will be explicitly exported to the stuff that cares
> (and nobody else) by the "module_init()" thing anyway.

but when I try to compile in the Bluetooth subsystem I got the following
error:

net/built-in.o: In function `sock_init':
net/built-in.o(.text.init+0x5b): undefined reference to `bluez_init'
make: *** [.tmp_vmlinux1] Error 1

It seems like that I have missed some magic to understand, because
"wanrouter_init" is also not declared static. But for netfilter or
netlink init it seems to work this way. Can you please give me some
infos how to fix this the right way.

Regards

Marcel



  parent reply	other threads:[~2002-10-07 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 20:46 [PATCH] Make it possible to compile in the Bluetooth subsystem Marcel Holtmann
2002-10-07 20:49 ` Linus Torvalds
2002-10-07 20:51   ` Linus Torvalds
2002-10-07 21:24   ` Marcel Holtmann [this message]
2002-10-07 21:28     ` Linus Torvalds
2002-10-07 22:38       ` Marcel Holtmann
2002-10-07 22:40 ` Maksim (Max) Krasnyanskiy

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=1034025872.861.81.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=torvalds@transmeta.com \
    /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