linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.20 Fix non-modular Bluetooth compilation
Date: Mon, 03 Jun 2002 16:46:07 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20020603162827.0831ad78@mail1.qualcomm.com> (raw)

Linus,

This trivial patch fixes linker error when Bluetooth support is compiled in.

Please apply.
Max

--- linux-2.5/net/bluetooth/af_bluetooth.c.old  Mon Jun  3 16:40:22 2002
+++ linux-2.5/net/bluetooth/af_bluetooth.c      Mon Jun  3 16:40:46 2002
@@ -317,7 +317,7 @@
         PF_BLUETOOTH, bluez_sock_create
  };

-static int __init bluez_init(void)
+int __init bluez_init(void)
  {
         BT_INFO("BlueZ Core ver %s Copyright (C) 2000,2001 Qualcomm Inc",
                  VERSION);



                 reply	other threads:[~2002-06-03 23:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5.1.0.14.2.20020603162827.0831ad78@mail1.qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).