Now that the module name bluetooth.o is not used by USB subsystem anymore

we can rename bluez.o to what it should have been from the begging 
bluetoth.o

net/bluetooth/Config.help

@@ -7,22 +7,22 @@ CONFIG_BLUEZ
   Bluetooth can be found at <http://www.bluetooth.com/>.
 
   Linux Bluetooth subsystem consist of several layers:
-               BlueZ Core (HCI device and connection manager, scheduler)
+               Bluetooth Core (HCI device and connection manager, scheduler)
                HCI Device drivers (interface to the hardware)
                L2CAP Module (L2CAP protocol)
                SCO Module (SCO links)
                RFCOMM Module (RFCOMM protocol)  
                BNEP Module (BNEP protocol)
 
-  Say Y here to enable Linux Bluetooth support and to build BlueZ Core
+  Say Y here to enable Linux Bluetooth support and to build Bluetooth Core
   layer.
 
   To use Linux Bluetooth subsystem, you will need several user-space
   utilities like hciconfig and hcid.  These utilities and updates to
-  Bluetooth kernel modules are provided in the BlueZ package.
+  Bluetooth kernel modules are provided in the BlueZ packages.
   For more information, see <http://bluez.sourceforge.net/>.
 
-  If you want to compile BlueZ Core as module (bluez.o) say M here.
+  If you want to compile Bluetooth Core as module (bluetooth.o) say M here.
 
 L2CAP protocol support
 CONFIG_BLUEZ_L2CAP

net/bluetooth/Makefile

@@ -4,12 +4,12 @@
 
 export-objs := syms.o
 
-obj-$(CONFIG_BLUEZ)		+= bluez.o
+obj-$(CONFIG_BLUEZ)		+= bluetooth.o
 obj-$(CONFIG_BLUEZ_L2CAP)	+= l2cap.o
 obj-$(CONFIG_BLUEZ_SCO)		+= sco.o
 obj-$(CONFIG_BLUEZ_RFCOMM)	+= rfcomm/
 obj-$(CONFIG_BLUEZ_BNEP)	+= bnep/
 
-bluez-objs := af_bluetooth.o hci_core.o hci_conn.o hci_event.o hci_sock.o lib.o syms.o
+bluetooth-objs := af_bluetooth.o hci_core.o hci_conn.o hci_event.o hci_sock.o lib.o syms.o
 
 include $(TOPDIR)/Rules.make