[PATCH] Change all <module>.o to .ko in Kconfig files

From:  GertJan Spoelman <kl@gjs.cc>

  OK, here is a new patch, I edited the old patch and took out the .ko's
  so now the extension is trimmed instead.

arch/alpha/Kconfig

@@ -635,7 +635,7 @@ config SRM_ENV
 	  of course).
 
 	  This driver is also available as a module and will be called
-	  srm_env.o then.
+	  srm_env then.
 
 config BINFMT_AOUT
 	tristate "Kernel support for a.out (ECOFF) binaries"
@@ -655,7 +655,7 @@ config BINFMT_AOUT
 	  QMAGIC support" then you'll have to say Y here. You may answer M to
 	  compile a.out support as a module and later load the module when you
 	  want to use a program or library in a.out format. The module will be
-	  called binfmt_aout.o. Saying M or N here is dangerous though,
+	  called binfmt_aout. Saying M or N here is dangerous though,
 	  because some crucial programs on your system might still be in A.OUT
 	  format.
 
@@ -693,7 +693,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -718,7 +718,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 config BINFMT_EM86
@@ -733,7 +733,7 @@ config BINFMT_EM86
 
 	  You may answer M to compile the emulation support as a module and
 	  later load the module when you want to use a Linux/Intel binary. The
-	  module will be called binfmt_em86.o. If unsure, say Y.
+	  module will be called binfmt_em86. If unsure, say Y.
 
 source "drivers/parport/Kconfig"
 
@@ -790,7 +790,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -826,7 +826,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -920,7 +920,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/arm/Kconfig

@@ -577,7 +577,7 @@ config FPE_NWFPE
 	  your machine has an FPA or floating point co-processor podule.
 
 	  It is also possible to say M to build the emulator as a module
-	  (nwfpe.o) or indeed to leave it out altogether. However, unless you
+	  (nwfpe) or indeed to leave it out altogether. However, unless you
 	  know what you are doing this can easily render your machine
 	  unbootable. Saying Y is the safe option.
 
@@ -599,7 +599,7 @@ config FPE_FASTFPE
 	  choose NWFPE.
 
 	  It is also possible to say M to build the emulator as a module
-	  (fastfpe.o).  But keep in mind that you should only load the FP
+	  (fastfpe).  But keep in mind that you should only load the FP
 	  emulator early in the bootup.  You should never change from NWFPE to
 	  FASTFPE or vice versa in an active system!
 
@@ -654,7 +654,7 @@ config BINFMT_AOUT
 	  QMAGIC support" then you'll have to say Y here. You may answer M to
 	  compile a.out support as a module and later load the module when you
 	  want to use a program or library in a.out format. The module will be
-	  called binfmt_aout.o. Saying M or N here is dangerous though,
+	  called binfmt_aout. Saying M or N here is dangerous though,
 	  because some crucial programs on your system might still be in A.OUT
 	  format.
 
@@ -684,7 +684,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -709,7 +709,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 config PM
@@ -804,7 +804,7 @@ config APM
 	  To compile this driver as a module ( = code which can be inserted in
 	  and removed from the running kernel whenever you want), say M here
 	  and read <file:Documentation/modules.txt>. The module will be called
-	  apm.o.
+	  apm.
 
 config ARTHUR
 	tristate "RISC OS personality"
@@ -814,7 +814,7 @@ config ARTHUR
 	  Acorn RISC OS/Arthur binaries under Linux. This code is still very
 	  experimental; if this sounds frightening, say N and sleep in peace.
 	  You can also say M here to compile this support as a module (which
-	  will be called arthur.o).
+	  will be called arthur).
 
 config CMDLINE
 	string "Default kernel command string"
@@ -946,7 +946,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -973,7 +973,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -1036,7 +1036,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/cris/Kconfig

@@ -55,7 +55,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config ETRAX_KGDB
@@ -587,7 +587,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -685,7 +685,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/cris/drivers/Kconfig

@@ -366,7 +366,7 @@ config PARPORT
 	  ( = code which can be inserted in and removed from the running
 	  kernel whenever you want), say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  parport.o.  If you have more than one parallel port and want to
+	  parport.  If you have more than one parallel port and want to
 	  specify which port and IRQ to be used by this driver at module load
 	  time, take a look at <file:Documentation/parport.txt>.
 
@@ -400,7 +400,7 @@ config PRINTER
 	  driver as a module however ( = code which can be inserted in and
 	  removed from the running kernel whenever you want), say M here and
 	  read <file:Documentation/modules.txt> and
-	  <file:Documentation/parport.txt>.  The module will be called lp.o.
+	  <file:Documentation/parport.txt>.  The module will be called lp.
 
 	  If you have several parallel ports, you can specify which ports to
 	  use with the "lp" kernel command line option.  (Try "man bootparam"
@@ -463,7 +463,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -494,7 +494,7 @@ config BLK_DEV_IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt> and
-	  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
+	  <file:Documentation/ide.txt>. The module will be called ide-mod.
 	  Do not compile this driver as a module if your root file system (the
 	  one containing the directory /) is located on an IDE device.
 
@@ -516,7 +516,7 @@ config BLK_DEV_IDEDISK
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ide-disk.o.  Do not compile this driver as a module
+	  will be called ide-disk.  Do not compile this driver as a module
 	  if your root file system (the one containing the directory /) is
 	  located on the IDE disk. If unsure, say Y.
 
@@ -544,7 +544,7 @@ config BLK_DEV_IDECD
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ide-cd.o.
+	  will be called ide-cd.
 
 config BLK_DEV_IDEDMA
 	bool
@@ -859,7 +859,7 @@ config USB
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called usbcore.o.  If you want to compile it as a
+	  The module will be called usbcore.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config ETRAX_USB_HOST_PORT1

arch/i386/Kconfig

@@ -573,7 +573,7 @@ config MICROCODE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called microcode.o.  If you want to compile it as
+	  The module will be called microcode.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.  If
 	  you use modprobe or kmod you may also want to add the line
 	  'alias char-major-10-184 microcode' to your /etc/modules.conf file.
@@ -859,7 +859,7 @@ config APM
 	  To compile this driver as a module ( = code which can be inserted in
 	  and removed from the running kernel whenever you want), say M here
 	  and read <file:Documentation/modules.txt>. The module will be called
-	  apm.o.
+	  apm.
 
 config APM_IGNORE_USER_SUSPEND
 	bool "Ignore USER SUSPEND"
@@ -1162,7 +1162,7 @@ config SCx200
 	  If you don't know what to do here, say N.
 
 	  This support is also available as a module.  If compiled as a
-	  module, it will be called scx200.o.
+	  module, it will be called scx200.
 
 source "drivers/pci/Kconfig"
 
@@ -1288,7 +1288,7 @@ config BINFMT_AOUT
 	  QMAGIC support" then you'll have to say Y here. You may answer M to
 	  compile a.out support as a module and later load the module when you
 	  want to use a program or library in a.out format. The module will be
-	  called binfmt_aout.o. Saying M or N here is dangerous though,
+	  called binfmt_aout. Saying M or N here is dangerous though,
 	  because some crucial programs on your system might still be in A.OUT
 	  format.
 
@@ -1318,7 +1318,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -1343,7 +1343,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 endmenu
@@ -1399,7 +1399,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -1426,7 +1426,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -1530,7 +1530,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/ia64/Kconfig

@@ -502,7 +502,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 if !IA64_HP_SIM
@@ -611,7 +611,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -640,7 +640,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)

arch/m68knommu/Kconfig

@@ -658,7 +658,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/mips/Kconfig

@@ -724,7 +724,7 @@ config BINFMT_AOUT
 	  QMAGIC support" then you'll have to say Y here. You may answer M to
 	  compile a.out support as a module and later load the module when you
 	  want to use a program or library in a.out format. The module will be
-	  called binfmt_aout.o. Saying M or N here is dangerous though,
+	  called binfmt_aout. Saying M or N here is dangerous though,
 	  because some crucial programs on your system might still be in A.OUT
 	  format.
 
@@ -755,7 +755,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -780,7 +780,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 source "drivers/pci/Kconfig"
@@ -875,7 +875,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -902,7 +902,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -994,7 +994,7 @@ config SERIAL
 
 	  If you want to compile this driver as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  serial.o.
+	  serial.
 	  [WARNING: Do not compile this driver as a module if you are using
 	  non-standard serial ports, since the configuration information will
 	  be lost when the driver is unloaded.  This limitation may be lifted
@@ -1157,7 +1157,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/mips64/Kconfig

@@ -361,7 +361,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config MIPS32_COMPAT
@@ -406,7 +406,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 endmenu
@@ -464,7 +464,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -491,7 +491,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -608,7 +608,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/parisc/Kconfig

@@ -199,7 +199,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -224,7 +224,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 endmenu
@@ -260,7 +260,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -327,7 +327,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/ppc/Kconfig

@@ -776,7 +776,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 source "drivers/pci/Kconfig"
@@ -989,9 +989,9 @@ config A2232
 	  for which 8 pin to DB25 adapters were supplied. The card also had
 	  jumpers internally to toggle various pinning configurations.
 
-	  This driver can be built as a module; but then "generic_serial.o"
+	  This driver can be built as a module; but then "generic_serial"
 	  will also be built as a module. This has to be loaded before
-	  "ser_a2232.o". If you want to do this, answer M here and read
+	  "ser_a2232". If you want to do this, answer M here and read
 	  "<file:Documentation/modules.txt>".
 
 config WHIPPET_SERIAL
@@ -1010,7 +1010,7 @@ config APNE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you
-	  want). The module is called apne.o. If you want to compile it as a
+	  want). The module is called apne. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIAL_CONSOLE
@@ -1192,7 +1192,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -1219,7 +1219,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -1428,7 +1428,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/ppc64/Kconfig

@@ -212,7 +212,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 source "drivers/pci/Kconfig"
@@ -311,7 +311,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -338,7 +338,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -404,7 +404,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/sh/Kconfig

@@ -623,7 +623,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -648,7 +648,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 source "drivers/parport/Kconfig"
@@ -704,7 +704,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -731,7 +731,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -855,7 +855,7 @@ config SERIAL
 
 	  If you want to compile this driver as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  serial.o.
+	  serial.
 	  [WARNING: Do not compile this driver as a module if you are using
 	  non-standard serial ports, since the configuration information will
 	  be lost when the driver is unloaded.  This limitation may be lifted
@@ -992,7 +992,7 @@ config PRINTER
 	  driver as a module however ( = code which can be inserted in and
 	  removed from the running kernel whenever you want), say M here and
 	  read <file:Documentation/modules.txt> and
-	  <file:Documentation/parport.txt>.  The module will be called lp.o.
+	  <file:Documentation/parport.txt>.  The module will be called lp.
 
 	  If you have several parallel ports, you can specify which ports to
 	  use with the "lp" kernel command line option.  (Try "man bootparam"
@@ -1036,7 +1036,7 @@ config PPDEV
 	  This support is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  ppdev.o.
+	  ppdev.
 
 	  If unsure, say N.
 
@@ -1108,7 +1108,7 @@ config SH_WDT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called shwdt.o. If you want to compile it as a module,
+	  The module is called shwdt. If you want to compile it as a module,
 	  say M here and read Documentation/modules.txt.
 
 endmenu
@@ -1137,7 +1137,7 @@ config RTC
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called rtc.o. If you want to compile it as a module,
+	  The module is called rtc. If you want to compile it as a module,
 	  say M here and read <file:Documentation/modules.txt>.
 
 source "drivers/char/pcmcia/Kconfig"
@@ -1175,7 +1175,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/sparc/Kconfig

@@ -182,8 +182,8 @@ config PCMCIA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  When compiled this way, there will be modules called pcmcia_core.o
-	  and ds.o.  If you want to compile it as a module, say M here and
+	  When compiled this way, there will be modules called pcmcia_core
+	  and ds.  If you want to compile it as a module, say M here and
 	  read <file:Documentation/modules.txt>.
 
 config SBUS
@@ -276,7 +276,7 @@ config SUN_OPENPROMFS
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want), say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called openpromfs.o.  If unsure, say M.
+	  The module will be called openpromfs.  If unsure, say M.
 
 config KCORE_ELF
 	bool
@@ -319,7 +319,7 @@ config BINFMT_AOUT
 	  QMAGIC support" then you'll have to say Y here. You may answer M to
 	  compile a.out support as a module and later load the module when you
 	  want to use a program or library in a.out format. The module will be
-	  called binfmt_aout.o. Saying M or N here is dangerous though,
+	  called binfmt_aout. Saying M or N here is dangerous though,
 	  because some crucial programs on your system might still be in A.OUT
 	  format.
 
@@ -349,7 +349,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -374,7 +374,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 config SUNOS_EMUL
@@ -404,7 +404,7 @@ config PRINTER
 	  driver as a module however ( = code which can be inserted in and
 	  removed from the running kernel whenever you want), say M here and
 	  read <file:Documentation/modules.txt> and
-	  <file:Documentation/parport.txt>.  The module will be called lp.o.
+	  <file:Documentation/parport.txt>.  The module will be called lp.
 
 	  If you have several parallel ports, you can specify which ports to
 	  use with the "lp" kernel command line option.  (Try "man bootparam"
@@ -442,7 +442,7 @@ config BLK_DEV_FD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called floppy.o. If you want to compile it as a
+	  The module will be called floppy. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config BLK_DEV_LOOP
@@ -492,7 +492,7 @@ config BLK_DEV_LOOP
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called loop.o.
+	  will be called loop.
 
 	  Most users will answer N here.
 
@@ -521,7 +521,7 @@ config BLK_DEV_NBD
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called nbd.o.
+	  will be called nbd.
 
 	  If unsure, say N.
 
@@ -543,7 +543,7 @@ config BLK_DEV_RAM
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M and read <file:Documentation/modules.txt>. The module will be
-	  called rd.o.
+	  called rd.
 
 	  Most normal users won't need the RAM disk functionality, and can
 	  thus say N here.
@@ -613,7 +613,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -644,7 +644,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -665,7 +665,7 @@ config BLK_DEV_SD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sd_mod.o.  If you want to compile it as a
+	  The module will be called sd_mod.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  Do not compile this driver as a
 	  module if your root file system (the one containing the directory /)
@@ -701,7 +701,7 @@ config CHR_DEV_ST
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called st.o. If you want to compile it as a
+	  The module will be called st. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.
 
@@ -726,7 +726,7 @@ config CHR_DEV_OSST
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called osst.o. If you want to compile it as a
+	  The module will be called osst. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.
 
@@ -741,7 +741,7 @@ config BLK_DEV_SR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sr_mod.o. If you want to compile it as a
+	  The module will be called sr_mod. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.
 
@@ -794,7 +794,7 @@ config CHR_DEV_SG
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt> and
-	  <file:Documentation/scsi/scsi.txt>. The module will be called sg.o.
+	  <file:Documentation/scsi/scsi.txt>. The module will be called sg.
 	  If unsure, say N.
 
 comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
@@ -856,7 +856,7 @@ config SCSI_SUNESP
 	  This is the driver for the Sun ESP SCSI host adapter. The ESP
 	  chipset is present in most SPARC SBUS-based computers.
 
-	  This support is also available as a module called esp.o ( = code
+	  This support is also available as a module called esp ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -870,7 +870,7 @@ config SCSI_QLOGICPTI
 	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
 	  driven by a different driver.
 
-	  This support is also available as a module called qlogicpti.o ( =
+	  This support is also available as a module called qlogicpti ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -963,7 +963,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.
@@ -992,7 +992,7 @@ config SOFT_WATCHDOG
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>. The module will be called
-	  softdog.o.
+	  softdog.
 
 endmenu
 

arch/v850/Kconfig

@@ -351,7 +351,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

arch/x86_64/Kconfig

@@ -427,7 +427,7 @@ config BINFMT_ELF
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called binfmt_elf.o. Saying M or N here is dangerous because
+	  will be called binfmt_elf. Saying M or N here is dangerous because
 	  some crucial programs on your system might be in ELF format.
 
 config BINFMT_MISC
@@ -452,7 +452,7 @@ config BINFMT_MISC
 	  use this part of the kernel.
 
 	  You may say M here for module support and later load the module when
-	  you have use for it; the module is called binfmt_misc.o. If you
+	  you have use for it; the module is called binfmt_misc. If you
 	  don't know what to answer at this point, say Y.
 
 config IA32_EMULATION
@@ -518,7 +518,7 @@ config IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called ide.o.
+	  will be called ide.
 
 	  For further information, please read <file:Documentation/ide.txt>.
 
@@ -545,7 +545,7 @@ config SCSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called scsi_mod.o.  If you want to compile it as
+	  The module will be called scsi_mod.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> and
 	  <file:Documentation/scsi/scsi.txt>.  However, do not compile this as a
 	  module if your root file system (the one containing the directory /)
@@ -615,7 +615,7 @@ config SOUND
 	  and load that module after the PnP configuration is finished.  To do
 	  this, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/sound/oss/README.modules>; the module will be
-	  called soundcore.o.
+	  called soundcore.
 
 	  I'm told that even without a sound card, you can make your computer
 	  say more than an occasional beep, by programming the PC speaker.

drivers/atm/Kconfig

@@ -34,7 +34,7 @@ config ATM_ENI
 
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
-	  <file:Documentation/modules.txt>.  The module will be called eni.o.
+	  <file:Documentation/modules.txt>.  The module will be called eni.
 
 config ATM_ENI_DEBUG
 	bool "Enable extended debugging"
@@ -141,7 +141,7 @@ config ATM_FIRESTREAM
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  firestream.o.
+	  firestream.
 
 config ATM_ZATM
 	tristate "ZeitNet ZN1221/ZN1225"
@@ -152,7 +152,7 @@ config ATM_ZATM
 
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
-	  <file:Documentation/modules.txt>.  The module will be called zatm.o.
+	  <file:Documentation/modules.txt>.  The module will be called zatm.
 
 config ATM_ZATM_DEBUG
 	bool "Enable extended debugging"
@@ -191,7 +191,7 @@ config ATM_NICSTAR
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>. The module will be called
-	  nicstar.o.
+	  nicstar.
 
 config ATM_NICSTAR_USE_SUNI
 	bool "Use suni PHY driver (155Mbps)"
@@ -223,7 +223,7 @@ config ATM_IDT77252
 
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
-	  <file:Documentation/modules.txt>. The module will be called idt77252.o
+	  <file:Documentation/modules.txt>. The module will be called idt77252
 
 config ATM_IDT77252_DEBUG
 	bool "Enable debugging messages"
@@ -256,7 +256,7 @@ config ATM_AMBASSADOR
 	depends on PCI
 	help
 	  This is a driver for ATMizer based ATM card produced by Madge
-	  Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
+	  Networks Ltd. Say Y (or M to compile as a module named ambassador)
 	  here if you have one of these cards.
 
 config ATM_AMBASSADOR_DEBUG
@@ -281,7 +281,7 @@ config ATM_HORIZON
 	help
 	  This is a driver for the Horizon chipset ATM adapter cards once
 	  produced by Madge Networks Ltd. Say Y (or M to compile as a module
-	  named horizon.o) here if you have one of these cards.
+	  named horizon) here if you have one of these cards.
 
 config ATM_HORIZON_DEBUG
 	bool "Enable debugging messages"
@@ -310,7 +310,7 @@ config ATM_IA
 	  UTP155, UTP25, DS3 and E3). Go to:
 	  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
 	  for more info about the cards. Say Y (or M to compile as a module
-	  named iphase.o) here if you have one of these cards.
+	  named iphase) here if you have one of these cards.
 
 	  See the file <file:Documentation/networking/iphase.txt> for further
 	  details.
@@ -339,7 +339,7 @@ config ATM_FORE200E_MAYBE
 	  This is a driver for the FORE Systems 200E-series ATM adapter
 	  cards. It simultaneously supports PCA-200E and SBA-200E models
 	  on PCI and SBUS hosts. Say Y (or M to compile as a module
-	  named fore_200e.o) here if you have one of these ATM adapters.
+	  named fore_200e) here if you have one of these ATM adapters.
 
 	  Note that the driver will actually be compiled only if you
 	  additionally enable the support for PCA-200E and/or SBA-200E

drivers/block/Kconfig

@@ -16,7 +16,7 @@ config BLK_DEV_FD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called floppy.o. If you want to compile it as a
+	  The module will be called floppy. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config AMIGA_FLOPPY
@@ -44,7 +44,7 @@ config BLK_DEV_PS2
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ps2esdi.o.
+	  will be called ps2esdi.
 
 config AMIGA_Z2RAM
 	tristate "Amiga Zorro II ramdisk support"
@@ -54,7 +54,7 @@ config AMIGA_Z2RAM
 	  ramdisk or as a swap partition. Say Y if you want to include this
 	  driver in the kernel. This driver is also available as a module
 	  ( = code which can be inserted in and removed from the running
-	  kernel whenever you want). The module is called z2ram.o. If you want
+	  kernel whenever you want). The module is called z2ram. If you want
 	  to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
 
@@ -74,7 +74,7 @@ config ATARI_ACSI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called acsi.o.
+	  The module will be called acsi.
 
 comment "Some devices (e.g. CD jukebox) support multiple LUNs"
 	depends on ATARI && ATARI_ACSI
@@ -98,7 +98,7 @@ config ATARI_SLM
 	  it in the kernel. Otherwise, say N. This driver is also available as
 	  a module ( = code which can be inserted in and removed from the
 	  running kernel whenever you want). The module will be called
-	  acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
+	  acsi_slm. Be warned: the driver needs much ST-RAM and can cause
 	  problems due to that fact!
 
 config BLK_DEV_XD
@@ -111,7 +111,7 @@ config BLK_DEV_XD
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called xd.o.
+	  will be called xd.
 
 	  It's pretty unlikely that you have one of these: say N.
 
@@ -133,7 +133,7 @@ config PARIDE
 	  PARIDE as a module. If you built PARIDE support into your kernel,
 	  you may still build the individual protocol modules and high-level
 	  drivers as loadable modules. If you build this support as a module,
-	  it will be called paride.o.
+	  it will be called paride.
 
 	  To use the PARIDE support, you must say Y or M here and also to at
 	  least one high-level driver (e.g. "Parallel port IDE disks",
@@ -190,7 +190,7 @@ config BLK_DEV_DAC960
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called DAC960.o.
+	  will be called DAC960.
 
 config BLK_DEV_UMEM
 	tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
@@ -206,7 +206,7 @@ config BLK_DEV_UMEM
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read Documentation/modules.txt. The module will be
-	  called umem.o.
+	  called umem.
 
 	  The umem driver has not yet been allocated a MAJOR number, so
 	  one is chosen dynamically.  Use "devfs" or look in /proc/devices
@@ -259,7 +259,7 @@ config BLK_DEV_LOOP
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called loop.o.
+	  will be called loop.
 
 	  Most users will answer N here.
 
@@ -288,7 +288,7 @@ config BLK_DEV_NBD
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>. The module
-	  will be called nbd.o.
+	  will be called nbd.
 
 	  If unsure, say N.
 
@@ -308,7 +308,7 @@ config BLK_DEV_RAM
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M and read <file:Documentation/modules.txt>. The module will be
-	  called rd.o.
+	  called rd.
 
 	  Most normal users won't need the RAM disk functionality, and can
 	  thus say N here.

drivers/block/paride/Kconfig

@@ -21,7 +21,7 @@ config PARIDE_PD
 	  connected through a parallel port. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  parallel port IDE driver, otherwise you should answer M to build
-	  it as a loadable module. The module will be called pd.o. You
+	  it as a loadable module. The module will be called pd. You
 	  must also have at least one parallel port protocol driver in your
 	  system. Among the devices supported by this driver are the SyQuest
 	  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
@@ -35,7 +35,7 @@ config PARIDE_PCD
 	  connected through a parallel port. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
-	  build it as a loadable module. The module will be called pcd.o. You
+	  build it as a loadable module. The module will be called pcd. You
 	  must also have at least one parallel port protocol driver in your
 	  system. Among the devices supported by this driver are the
 	  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
@@ -51,7 +51,7 @@ config PARIDE_PF
 	  connected through a parallel port. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  parallel port ATAPI disk driver, otherwise you should answer M
-	  to build it as a loadable module. The module will be called pf.o.
+	  to build it as a loadable module. The module will be called pf.
 	  You must also have at least one parallel port protocol driver in
 	  your system. Among the devices supported by this driver are the
 	  MicroSolutions backpack PD/CD drive and the Imation Superdisk
@@ -65,7 +65,7 @@ config PARIDE_PT
 	  connected through a parallel port. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  parallel port ATAPI disk driver, otherwise you should answer M
-	  to build it as a loadable module. The module will be called pt.o.
+	  to build it as a loadable module. The module will be called pt.
 	  You must also have at least one parallel port protocol driver in
 	  your system. Among the devices supported by this driver is the
 	  parallel port version of the HP 5GB drive.
@@ -82,7 +82,7 @@ config PARIDE_PG
 	  If you chose to build PARIDE support into your kernel, you may
 	  answer Y here to build in the parallel port generic ATAPI driver,
 	  otherwise you should answer M to build it as a loadable module. The
-	  module will be called pg.o.
+	  module will be called pg.
 
 	  You must also have at least one parallel port protocol driver in
 	  your system.
@@ -106,7 +106,7 @@ config PARIDE_ATEN
 	  parallel port kits made in Hong Kong. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  protocol driver, otherwise you should answer M to build it as a
-	  loadable module. The module will be called aten.o. You must also
+	  loadable module. The module will be called aten. You must also
 	  have a high-level driver for the type of device that you want to
 	  support.
 
@@ -125,7 +125,7 @@ config PARIDE_BPCK
 	  If you chose to build PARIDE support into your kernel, you may
 	  answer Y here to build in the protocol driver, otherwise you should
 	  answer M to build it as a loadable module.  The module will be
-	  called bpck.o.  You must also have a high-level driver for the type
+	  called bpck.  You must also have a high-level driver for the type
 	  of device that you want to support.
 
 config PARIDE_BPCK6
@@ -144,7 +144,7 @@ config PARIDE_BPCK6
 	  If you chose to build PARIDE support into your kernel, you may
 	  answer Y here to build in the protocol driver, otherwise you should
 	  answer M to build it as a loadable module.  The module will be
-	  called bpck6.o.  You must also have a high-level driver for the type
+	  called bpck6.  You must also have a high-level driver for the type
 	  of device that you want to support.
 
 config PARIDE_COMM
@@ -155,7 +155,7 @@ config PARIDE_COMM
 	  protocol from DataStor. If you chose to build PARIDE support
 	  into your kernel, you may answer Y here to build in the protocol
 	  driver, otherwise you should answer M to build it as a loadable
-	  module. The module will be called comm.o. You must also have
+	  module. The module will be called comm. You must also have
 	  a high-level driver for the type of device that you want to support.
 
 config PARIDE_DSTR
@@ -166,7 +166,7 @@ config PARIDE_DSTR
 	  protocol from DataStor. If you chose to build PARIDE support
 	  into your kernel, you may answer Y here to build in the protocol
 	  driver, otherwise you should answer M to build it as a loadable
-	  module. The module will be called dstr.o. You must also have
+	  module. The module will be called dstr. You must also have
 	  a high-level driver for the type of device that you want to support.
 
 config PARIDE_FIT2
@@ -178,7 +178,7 @@ config PARIDE_FIT2
 	  (low speed) adapter that is used in some portable hard drives. If
 	  you chose to build PARIDE support into your kernel, you may answer Y
 	  here to build in the protocol driver, otherwise you should answer M
-	  to build it as a loadable module. The module will be called ktti.o.
+	  to build it as a loadable module. The module will be called ktti.
 	  You must also have a high-level driver for the type of device that
 	  you want to support.
 
@@ -192,7 +192,7 @@ config PARIDE_FIT3
 	  devices. If you chose to build PARIDE support into your kernel, you
 	  may answer Y here to build in the protocol driver, otherwise you
 	  should answer M to build it as a loadable module. The module will be
-	  called fit3.o. You must also have a high-level driver for the type
+	  called fit3. You must also have a high-level driver for the type
 	  of device that you want to support.
 
 config PARIDE_EPAT
@@ -205,7 +205,7 @@ config PARIDE_EPAT
 	  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
 	  PARIDE support into your kernel, you may answer Y here to build in
 	  the protocol driver, otherwise you should answer M to build it as a
-	  loadable module. The module will be called epat.o. You must also
+	  loadable module. The module will be called epat. You must also
 	  have a high-level driver for the type of device that you want to
 	  support.
 
@@ -226,7 +226,7 @@ config PARIDE_EPIA
 	  found in some no-name kits. If you chose to build PARIDE support
 	  into your kernel, you may answer Y here to build in the protocol
 	  driver, otherwise you should answer M to build it as a loadable
-	  module. The module will be called epia.o. You must also have a
+	  module. The module will be called epia. You must also have a
 	  high-level driver for the type of device that you want to support.
 
 config PARIDE_FRIQ
@@ -238,7 +238,7 @@ config PARIDE_FRIQ
 	  drive.  If you chose to build PARIDE support into your kernel, you
 	  may answer Y here to build in the protocol driver, otherwise you
 	  should answer M to build it as a loadable module. The module will be
-	  called friq.o. You must also have a high-level driver for the type
+	  called friq. You must also have a high-level driver for the type
 	  of device that you want to support.
 
 config PARIDE_FRPW
@@ -249,7 +249,7 @@ config PARIDE_FRPW
 	  protocol. If you chose to build PARIDE support into your kernel, you
 	  may answer Y here to build in the protocol driver, otherwise you
 	  should answer M to build it as a loadable module. The module will be
-	  called frpw.o. You must also have a high-level driver for the type
+	  called frpw. You must also have a high-level driver for the type
 	  of device that you want to support.
 
 config PARIDE_KBIC
@@ -262,7 +262,7 @@ config PARIDE_KBIC
 	  especially in Europe. If you chose to build PARIDE support into your
 	  kernel, you may answer Y here to build in the protocol driver,
 	  otherwise you should answer M to build it as a loadable module. The
-	  module will be called kbic.o. You must also have a high-level driver
+	  module will be called kbic. You must also have a high-level driver
 	  for the type of device that you want to support.
 
 config PARIDE_KTTI
@@ -274,7 +274,7 @@ config PARIDE_KTTI
 	  used in some 2.5" portable hard drives. If you chose to build PARIDE
 	  support into your kernel, you may answer Y here to build in the
 	  protocol driver, otherwise you should answer M to build it as a
-	  loadable module. The module will be called ktti.o. You must also
+	  loadable module. The module will be called ktti. You must also
 	  have a high-level driver for the type of device that you want to
 	  support.
 
@@ -287,7 +287,7 @@ config PARIDE_ON20
 	  name). If you chose to build PARIDE support into your kernel, you
 	  may answer Y here to build in the protocol driver, otherwise you
 	  should answer M to build it as a loadable module. The module will
-	  be called on20.o. You must also have a high-level driver for the
+	  be called on20. You must also have a high-level driver for the
 	  type of device that you want to support.
 
 config PARIDE_ON26
@@ -299,7 +299,7 @@ config PARIDE_ON26
 	  name). If you chose to build PARIDE support into your kernel, you
 	  may answer Y here to build in the protocol driver, otherwise you
 	  should answer M to build it as a loadable module. The module will be
-	  called on26.o. You must also have a high-level driver for the type
+	  called on26. You must also have a high-level driver for the type
 	  of device that you want to support.
 
 #

drivers/bluetooth/Kconfig

@@ -11,7 +11,7 @@ config BT_HCIUSB
 	  USB interface.
 
 	  Say Y here to compile support for Bluetooth USB devices into the
-	  kernel or say M to compile it as module (hci_usb.o).
+	  kernel or say M to compile it as module (hci_usb).
 
 config BT_USB_ZERO_PACKET
 	bool "USB zero packet support"
@@ -34,7 +34,7 @@ config BT_HCIUART
 	  adapter and BrainBoxes Bluetooth PC Card.
 
 	  Say Y here to compile support for Bluetooth UART devices into the
-	  kernel or say M to compile it as module (hci_uart.o).
+	  kernel or say M to compile it as module (hci_uart).
 
 config BT_HCIUART_H4
 	bool "UART (H4) protocol support"
@@ -68,7 +68,7 @@ config BT_HCIDTL1
 	  Socket Bluetooth CF Card
 
 	  Say Y here to compile support for HCI DTL1 devices into the
-	  kernel or say M to compile it as module (dtl1_cs.o).
+	  kernel or say M to compile it as module (dtl1_cs).
 
 config BT_HCIBT3C
 	tristate "HCI BT3C (PC Card) driver"
@@ -84,7 +84,7 @@ config BT_HCIBT3C
 	  the BlueFW package. For more information, see <http://bluez.sf.net>.
 
 	  Say Y here to compile support for HCI BT3C devices into the
-	  kernel or say M to compile it as module (bt3c_cs.o).
+	  kernel or say M to compile it as module (bt3c_cs).
 
 config BT_HCIBLUECARD
 	tristate "HCI BlueCard (PC Card) driver"
@@ -97,7 +97,7 @@ config BT_HCIBLUECARD
 	  Anycom Bluetooth CF Card
 
 	  Say Y here to compile support for HCI BlueCard devices into the
-	  kernel or say M to compile it as module (bluecard_cs.o).
+	  kernel or say M to compile it as module (bluecard_cs).
 
 config BT_HCIVHCI
 	tristate "HCI VHCI (Virtual HCI device) driver"
@@ -107,7 +107,7 @@ config BT_HCIVHCI
 	  This driver is required if you want to use HCI Emulation software.
 
 	  Say Y here to compile support for virtual HCI devices into the
-	  kernel or say M to compile it as module (hci_vhci.o).
+	  kernel or say M to compile it as module (hci_vhci).
 
 endmenu
 

drivers/cdrom/Kconfig

@@ -18,7 +18,7 @@ config AZTCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called aztcd.o.  If you want to compile it as a
+	  The module will be called aztcd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config GSCD
@@ -36,7 +36,7 @@ config GSCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gscd.o.  If you want to compile it as a
+	  The module will be called gscd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SBPCD
@@ -76,7 +76,7 @@ config SBPCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sbpcd.o.  If you want to compile it as a
+	  The module will be called sbpcd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config MCD
@@ -101,7 +101,7 @@ config MCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called mcd.o. If you want to compile it as a
+	  The module will be called mcd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config MCD_IRQ
@@ -142,7 +142,7 @@ config MCDX
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called mcdx.o. If you want to compile it as a
+	  The module will be called mcdx. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config OPTCD
@@ -161,7 +161,7 @@ config OPTCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called optcd.o. If you want to compile it as a
+	  The module will be called optcd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config CM206
@@ -178,7 +178,7 @@ config CM206
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cm206.o. If you want to compile it as a
+	  The module will be called cm206. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SJCD
@@ -192,7 +192,7 @@ config SJCD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sjcd.o. If you want to compile it as a
+	  The module will be called sjcd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config ISP16_CDI
@@ -207,7 +207,7 @@ config ISP16_CDI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called isp16.o. If you want to compile it as a
+	  The module will be called isp16. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config CDU31A
@@ -229,7 +229,7 @@ config CDU31A
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cdu31a.o.  If you want to compile it as a
+	  The module will be called cdu31a.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config CDU535
@@ -245,6 +245,6 @@ config CDU535
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sonycd535.o. If you want to compile it as
+	  The module will be called sonycd535. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 

drivers/char/agp/Kconfig

@@ -23,7 +23,7 @@ config AGP
 
 	  This driver is available as a module.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.  The
-	  module will be called agpgart.o.
+	  module will be called agpgart.
 
 config AGP_GART
 	bool "/dev/agpgart (AGP Support)"

drivers/char/drm/Kconfig

@@ -20,7 +20,7 @@ config DRM_TDFX
 	depends on DRM
 	help
 	  Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
-	  graphics card.  If M is selected, the module will be called tdfx.o.
+	  graphics card.  If M is selected, the module will be called tdfx.
 
 #    tristate '  3dlabs GMX 2000' CONFIG_DRM_GAMMA
 config DRM_R128
@@ -28,7 +28,7 @@ config DRM_R128
 	depends on DRM
 	help
 	  Choose this option if you have an ATI Rage 128 graphics card.  If M
-	  is selected, the module will be called r128.o.  AGP support for
+	  is selected, the module will be called r128.  AGP support for
 	  this card is strongly suggested (unless you have a PCI version).
 
 config DRM_RADEON
@@ -39,14 +39,14 @@ config DRM_RADEON
 	  are both PCI and AGP versions.  You don't need to choose this to
 	  run the Radeon in plain VGA mode.  There is a product page at
 	  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
-	  If M is selected, the module will be called radeon.o.
+	  If M is selected, the module will be called radeon.
 
 config DRM_I810
 	tristate "Intel I810"
 	depends on DRM && AGP
 	help
 	  Choose this option if you have an Intel I810 graphics card.  If M is
-	  selected, the module will be called i810.o.  AGP support is required
+	  selected, the module will be called i810.  AGP support is required
 	  for this driver to work.
 
 config DRM_I830
@@ -58,6 +58,6 @@ config DRM_MGA
 	depends on DRM && AGP
 	help
 	  Choose this option if you have a Matrox G200, G400 or G450 graphics
-	  card.  If M is selected, the module will be called mga.o.  AGP
+	  card.  If M is selected, the module will be called mga.  AGP
 	  support is required for this driver to work.
 

drivers/char/ftape/Kconfig

@@ -18,14 +18,14 @@ config ZFTAPE
 	  module ( = code which can be inserted in and removed from the
 	  running kernel whenever you want).  In this case you should read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  zftape.o.
+	  zftape.
 
 	  Regardless of whether you say Y or M here, an additional runtime
-	  loadable module called `zft-compressor.o' which contains code to
+	  loadable module called `zft-compressor' which contains code to
 	  support user transparent on-the-fly compression based on Ross
 	  William's lzrw3 algorithm will be produced.  If you have enabled the
 	  kernel module loader (i.e. have said Y to "Kernel module loader
-	  support", above) then `zft-compressor.o' will be loaded
+	  support", above) then `zft-compressor' will be loaded
 	  automatically by zftape when needed.
 
 	  Despite its name, zftape does NOT use compression by default.  The

drivers/char/pcmcia/Kconfig

@@ -15,7 +15,7 @@ config SYNCLINK_CS
 
 	  This driver may be built as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called synclinkmp.o.  If you want to do that, say M
+	  The module will be called synclinkmp.  If you want to do that, say M
 	  here.
 
 endmenu

drivers/char/watchdog/Kconfig

@@ -50,7 +50,7 @@ config SOFT_WATCHDOG
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>. The module will be called
-	  softdog.o.
+	  softdog.
 
 config WDT
 	tristate "WDT Watchdog timer"
@@ -66,7 +66,7 @@ config WDT
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called wdt.o.
+	  will be called wdt.
 
 config WDTPCI
 	tristate "WDT PCI Watchdog timer"
@@ -82,7 +82,7 @@ config WDTPCI
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called wdt_pci.o.
+	  will be called wdt_pci.
 
 config WDT_501
 	bool "WDT501 features"
@@ -115,7 +115,7 @@ config PCWATCHDOG
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called pcwd.o. If you want to compile it as a module,
+	  The module is called pcwd. If you want to compile it as a module,
 	  say M here and read <file:Documentation/modules.txt>.
 
 	  Most people will say N.
@@ -132,7 +132,7 @@ config ACQUIRE_WDT
 	  This driver is like the WDT501 driver but for different hardware.
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called pscwdt.o.  If you want to compile it as a
+	  The module is called pscwdt.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.  Most
 	  people will say N.
 
@@ -150,7 +150,7 @@ config 21285_WATCHDOG
 	help
 	  The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
 	  here if you wish to use this. Alternatively say M to compile the
-	  driver as a module, which will be called wdt285.o.
+	  driver as a module, which will be called wdt285.
 
 	  This driver does not work on all machines. In particular, early CATS
 	  boards have hardware problems that will cause the machine to simply
@@ -164,7 +164,7 @@ config 977_WATCHDOG
 	help
 	  Say Y here to include support for the WB977 watchdog included in
 	  NetWinder machines. Alternatively say M to compile the driver as
-	  a module, which will be called wdt977.o.
+	  a module, which will be called wdt977.
 
 	  Not sure? It's safe to say N.
 
@@ -179,7 +179,7 @@ config SA1100_WATCHDOG
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to compile it as a module, say M here and read
-	  Documentation/modules.txt. The module will be called sa1100_wdt.o.
+	  Documentation/modules.txt. The module will be called sa1100_wdt.
 
 config EUROTECH_WDT
 	tristate "Eurotech CPU-1220/1410 Watchdog Timer"
@@ -202,7 +202,7 @@ config IB700_WDT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called ib700wdt.o. If you want to compile it as a
+	  The module is called ib700wdt. If you want to compile it as a
 	  module, say M here and read Documentation/modules.txt. Most people
 	  will say N.
 
@@ -225,7 +225,7 @@ config I810_TCO
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  i810-tco.o.
+	  i810-tco.
 
 config MIXCOMWD
 	tristate "Mixcom Watchdog"
@@ -238,7 +238,7 @@ config MIXCOMWD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called mixcomwd.o.  If you want to compile it as a
+	  The module is called mixcomwd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.  Most
 	  people will say N.
 
@@ -249,7 +249,7 @@ config SCx200_WDT
 	  Enable the built-in watchdog timer support on the National 
 	  Semiconductor SCx200 processors.
 
-	  If compiled as a module, it will be called scx200_watchdog.o.
+	  If compiled as a module, it will be called scx200_watchdog.
 
 config 60XX_WDT
 	tristate "SBC-60XX Watchdog Timer"
@@ -263,7 +263,7 @@ config 60XX_WDT
 	  you can probably make this driver work with your card as well.
 
 	  You can compile this driver directly into the kernel, or use
-	  it as a module.  The module will be called sbc60xxwdt.o.
+	  it as a module.  The module will be called sbc60xxwdt.
 
 config W83877F_WDT
 	tristate "W83877F (EMACS) Watchdog Timer"
@@ -277,7 +277,7 @@ config W83877F_WDT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called mixcomwd.o.  If you want to compile it as a
+	  The module is called mixcomwd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.  Most
 	  people will say N.
 
@@ -293,7 +293,7 @@ config MACHZ_WDT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module is called machzwd.o.  If you want to compile it as a
+	  The module is called machzwd.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config W83877F_WDT

drivers/fc4/Kconfig

@@ -33,7 +33,7 @@ config FC4_SOC
 	  that if you have older firmware in the card, you'll need the
 	  microcode from the Solaris driver to make it work.
 
-	  This support is also available as a module called soc.o ( = code
+	  This support is also available as a module called soc ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -48,7 +48,7 @@ config FC4_SOCAL
 	  Interface Board). You'll probably need the microcode from the
 	  Solaris driver to make it work.
 
-	  This support is also available as a module called socal.o ( = code
+	  This support is also available as a module called socal ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -62,7 +62,7 @@ config SCSI_PLUTO
 	help
 	  If you never bought a disk array made by Sun, go with N.
 
-	  This support is also available as a module called pluto.o ( = code
+	  This support is also available as a module called pluto ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -76,7 +76,7 @@ config SCSI_FCAL
 	  common is either A5000 array or internal disks in E[3-6]000
 	  machines.
 
-	  This support is also available as a module called fcal.o ( = code
+	  This support is also available as a module called fcal ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>. If unsure, say N.

drivers/hotplug/Kconfig

@@ -16,7 +16,7 @@ config HOTPLUG_PCI
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called pci_hotplug.o. If you want to compile it
+	  The module will be called pci_hotplug. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -30,7 +30,7 @@ config HOTPLUG_PCI_COMPAQ
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cpqphp.o. If you want to compile it
+	  The module will be called cpqphp. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -54,7 +54,7 @@ config HOTPLUG_PCI_IBM
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cpqphp.o. If you want to compile it
+	  The module will be called cpqphp. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -68,7 +68,7 @@ config HOTPLUG_PCI_ACPI
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called acpiphp.o. If you want to compile it
+	  The module will be called acpiphp. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -82,7 +82,7 @@ config HOTPLUG_PCI_CPCI
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cpci_hotplug.o. If you want to compile it
+	  The module will be called cpci_hotplug. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -96,7 +96,7 @@ config HOTPLUG_PCI_CPCI_ZT5550
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cpcihp_zt5550.o. If you want to compile it
+	  The module will be called cpcihp_zt5550. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.
@@ -111,7 +111,7 @@ config HOTPLUG_PCI_CPCI_GENERIC
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cpcihp_generic.o. If you want to compile it
+	  The module will be called cpcihp_generic. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  When in doubt, say N.

drivers/i2c/Kconfig

@@ -27,7 +27,7 @@ config I2C
 	  This I2C support is also available as a module.  If you want to
 	  compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-core.o.
+	  The module will be called i2c-core.
 
 config I2C_ALGOBIT
 	tristate "I2C bit-banging interfaces"
@@ -40,7 +40,7 @@ config I2C_ALGOBIT
 	  This support is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-algo-bit.o.
+	  The module will be called i2c-algo-bit.
 
 config I2C_PHILIPSPAR
 	tristate "Philips style parallel port adapter"
@@ -52,7 +52,7 @@ config I2C_PHILIPSPAR
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-philips-par.o.
+	  The module will be called i2c-philips-par.
 
 	  Note that if you want support for different parallel port devices,
 	  life will be much easier if you compile them all as modules.
@@ -67,7 +67,7 @@ config I2C_ELV
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-elv.o.
+	  The module will be called i2c-elv.
 
 config I2C_VELLEMAN
 	tristate "Velleman K9000 adapter"
@@ -79,7 +79,7 @@ config I2C_VELLEMAN
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-velleman.o.
+	  The module will be called i2c-velleman.
 
 config SCx200_I2C
 	tristate "NatSemi SCx200 I2C using GPIO pins"
@@ -89,7 +89,7 @@ config SCx200_I2C
 
 	  If you don't know what to do here, say N.
 
-	  If compiled as a module, it will be called scx200_i2c.o.
+	  If compiled as a module, it will be called scx200_i2c.
 
 config SCx200_I2C_SCL
 	int "GPIO pin used for SCL"
@@ -115,7 +115,7 @@ config SCx200_ACB
 
 	  If you don't know what to do here, say N.
 
-	  If compiled as a module, it will be called scx200_acb.o.
+	  If compiled as a module, it will be called scx200_acb.
 
 config I2C_ALGOPCF
 	tristate "I2C PCF 8584 interfaces"
@@ -128,7 +128,7 @@ config I2C_ALGOPCF
 	  This support is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-algo-pcf.o.
+	  The module will be called i2c-algo-pcf.
 
 config I2C_ELEKTOR
 	tristate "Elektor ISA card"
@@ -140,7 +140,7 @@ config I2C_ELEKTOR
 	  This driver is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-elektor.o.
+	  The module will be called i2c-elektor.
 
 config ITE_I2C_ALGO
 	tristate "ITE I2C Algorithm"
@@ -194,7 +194,7 @@ config I2C_CHARDEV
 	  This code is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called i2c-dev.o.
+	  The module will be called i2c-dev.
 
 config I2C_PROC
 	tristate "I2C /proc interface (required for hardware sensors)"
@@ -205,7 +205,7 @@ config I2C_PROC
 
 	  This code is also available as a module. If you want to compile
 	  it as a module, say M here and read <file:Documentation/modules.txt>.
-	  The module will be called i2c-proc.o.
+	  The module will be called i2c-proc.
 
 	source drivers/i2c/busses/Kconfig
 	source drivers/i2c/chips/Kconfig

drivers/i2c/busses/Kconfig

@@ -16,7 +16,7 @@ config I2C_AMD756
 	  while the kernel is running.  If you want to compile it as a module,
 	  say M here and read <file:Documentation/modules.txt>.
 
-	  The module will be called i2c-amd756.o.
+	  The module will be called i2c-amd756.
 
 	  You will also need the latest user-space utilties: you can find them
 	  in the lm_sensors package, which you can download at 
@@ -33,7 +33,7 @@ config I2C_AMD8111
 	  while the kernel is running.  If you want to compile it as a module,
 	  say M here and read <file:Documentation/modules.txt>.
 
-	  The module will be called i2c-amd8111.o.
+	  The module will be called i2c-amd8111.
 
 	  You will also need the latest user-space utilties: you can find them
 	  in the lm_sensors package, which you can download at 

drivers/i2c/chips/Kconfig

@@ -16,7 +16,7 @@ config SENSORS_ADM1021
 	  be built as a module which can be inserted and removed while the 
 	  kernel is running.
 
-	  The module will be called adm1021.o.
+	  The module will be called adm1021.
 	  
 	  You will also need the latest user-space utilties: you can find them
 	  in the lm_sensors package, which you can download at 
@@ -31,7 +31,7 @@ config SENSORS_LM75
 	  TCN75, and National Semi LM77. This can also be built as a module
 	  which can be inserted and removed while the kernel is running.
 
-	  The module will be called lm75.o.
+	  The module will be called lm75.
 
 	  You will also need the latest user-space utilties: you can find them
 	  in the lm_sensors package, which you can download at 

drivers/ide/Kconfig

@@ -31,7 +31,7 @@ config BLK_DEV_IDE
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt> and
-	  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
+	  <file:Documentation/ide.txt>. The module will be called ide-mod.
 	  Do not compile this driver as a module if your root file system (the
 	  one containing the directory /) is located on an IDE device.
 
@@ -77,7 +77,7 @@ config BLK_DEV_IDEDISK
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ide-disk.o.  Do not compile this driver as a module
+	  will be called ide-disk.  Do not compile this driver as a module
 	  if your root file system (the one containing the directory /) is
 	  located on the IDE disk. If unsure, say Y.
 
@@ -136,7 +136,7 @@ config BLK_DEV_IDECD
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ide-cd.o.
+	  will be called ide-cd.
 
 #dep_tristate '  Include IDE/ATAPI TAPE support' CONFIG_BLK_DEV_IDETAPE $CONFIG_BLK_DEV_IDE
 config BLK_DEV_IDEFLOPPY
@@ -162,7 +162,7 @@ config BLK_DEV_IDEFLOPPY
 	  If you want to compile the driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ide-floppy.o.
+	  will be called ide-floppy.
 
 config BLK_DEV_IDESCSI
 	tristate "SCSI emulation support"

drivers/ieee1394/Kconfig

@@ -18,7 +18,7 @@ config IEEE1394
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ieee1394.o.
+	  will be called ieee1394.
 
 comment "Subsystem Options"
 	depends on IEEE1394
@@ -67,7 +67,7 @@ config IEEE1394_PCILYNX
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called pcilynx.o.
+	  will be called pcilynx.
 
 # Non-maintained pcilynx options
 # if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then
@@ -87,7 +87,7 @@ config IEEE1394_OHCI1394
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called ohci1394.o.
+	  will be called ohci1394.
 
 comment "Protocol Drivers"
 	depends on IEEE1394
@@ -131,7 +131,7 @@ config IEEE1394_DV1394
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called dv1394.o.
+	  will be called dv1394.
 
 config IEEE1394_RAWIO
 	tristate "Raw IEEE1394 I/O support"
@@ -145,7 +145,7 @@ config IEEE1394_RAWIO
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called raw1394.o.
+	  will be called raw1394.
 
 config IEEE1394_CMP
 	tristate "IEC61883-1 Plug support"
@@ -157,7 +157,7 @@ config IEEE1394_CMP
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called amdtp.o.
+	  will be called amdtp.
 
 config IEEE1394_AMDTP
 	tristate "IEC61883-6 (Audio transmission) support"
@@ -172,6 +172,6 @@ config IEEE1394_AMDTP
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called amdtp.o.
+	  will be called amdtp.
 
 endmenu

drivers/input/Kconfig

@@ -21,7 +21,7 @@ config INPUT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called input.o. If you want to compile it as a
+	  The module will be called input. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 comment "Userland interfaces"
@@ -41,7 +41,7 @@ config INPUT_MOUSEDEV
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called mousedev.o. If you want to compile it as
+	  The module will be called mousedev. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_MOUSEDEV_PSAUX
@@ -82,7 +82,7 @@ config INPUT_JOYDEV
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called joydev.o. If you want to compile it as a
+	  The module will be called joydev. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_TSDEV
@@ -97,7 +97,7 @@ config INPUT_TSDEV
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tsdev.o. If you want to compile it as a
+	  The module will be called tsdev. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_TSDEV_SCREEN_X
@@ -119,7 +119,7 @@ config INPUT_EVDEV
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called evdev.o. If you want to compile it as a
+	  The module will be called evdev. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_EVBUG
@@ -136,7 +136,7 @@ config INPUT_EVBUG
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called joydev.o. If you want to compile it as a
+	  The module will be called joydev. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 comment "Input I/O drivers"

drivers/input/gameport/Kconfig

@@ -18,7 +18,7 @@ config GAMEPORT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gameport.o. If you want to compile it as
+	  The module will be called gameport. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config SOUND_GAMEPORT
@@ -36,7 +36,7 @@ config GAMEPORT_NS558
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called ns558.o. If you want to compile it as a
+	  The module will be called ns558. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config GAMEPORT_L4
@@ -47,7 +47,7 @@ config GAMEPORT_L4
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called lightning.o. If you want to compile it as
+	  The module will be called lightning. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config GAMEPORT_EMU10K1
@@ -59,7 +59,7 @@ config GAMEPORT_EMU10K1
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called emu10k1-gp.o. If you want to compile it as
+	  The module will be called emu10k1-gp. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config GAMEPORT_VORTEX
@@ -71,7 +71,7 @@ config GAMEPORT_VORTEX
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called vortex.o. If you want to compile it as a
+	  The module will be called vortex. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config GAMEPORT_FM801

drivers/input/joystick/Kconfig

@@ -29,7 +29,7 @@ config JOYSTICK_ANALOG
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called analog.o. If you want to compile it as a
+	  The module will be called analog. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_A3D
@@ -41,7 +41,7 @@ config JOYSTICK_A3D
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called a3d.o. If you want to compile it as a
+	  The module will be called a3d. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_ADI
@@ -53,7 +53,7 @@ config JOYSTICK_ADI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called adi.o. If you want to compile it as a
+	  The module will be called adi. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_COBRA
@@ -64,7 +64,7 @@ config JOYSTICK_COBRA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cobra.o. If you want to compile it as a
+	  The module will be called cobra. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_GF2K
@@ -76,7 +76,7 @@ config JOYSTICK_GF2K
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gf2k.o. If you want to compile it as a
+	  The module will be called gf2k. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_GRIP
@@ -88,7 +88,7 @@ config JOYSTICK_GRIP
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called grip.o. If you want to compile it as a
+	  The module will be called grip. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_GRIP_MP
@@ -100,7 +100,7 @@ config JOYSTICK_GRIP_MP
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called grip_mp.o. If you want to compile it as a
+	  The module will be called grip_mp. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_GUILLEMOT
@@ -112,7 +112,7 @@ config JOYSTICK_GUILLEMOT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called guillemot.o. If you want to compile it as a
+	  The module will be called guillemot. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_INTERACT
@@ -124,7 +124,7 @@ config JOYSTICK_INTERACT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called interact.o. If you want to compile it as
+	  The module will be called interact. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_SIDEWINDER
@@ -136,7 +136,7 @@ config JOYSTICK_SIDEWINDER
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sidewinder.o. If you want to compile it
+	  The module will be called sidewinder. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_TMDC
@@ -148,7 +148,7 @@ config JOYSTICK_TMDC
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tmdc.o. If you want to compile it as a
+	  The module will be called tmdc. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 source "drivers/input/joystick/iforce/Kconfig"
@@ -162,7 +162,7 @@ config JOYSTICK_WARRIOR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called warrior.o. If you want to compile it as a
+	  The module will be called warrior. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_MAGELLAN
@@ -174,7 +174,7 @@ config JOYSTICK_MAGELLAN
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called magellan.o. If you want to compile it as
+	  The module will be called magellan. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_SPACEORB
@@ -186,7 +186,7 @@ config JOYSTICK_SPACEORB
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called spaceorb.o. If you want to compile it as
+	  The module will be called spaceorb. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_SPACEBALL
@@ -199,7 +199,7 @@ config JOYSTICK_SPACEBALL
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called spaceball.o. If you want to compile it as
+	  The module will be called spaceball. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_STINGER
@@ -211,7 +211,7 @@ config JOYSTICK_STINGER
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called stinger.o. If you want to compile it as a
+	  The module will be called stinger. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_TWIDDLER
@@ -223,7 +223,7 @@ config JOYSTICK_TWIDDLER
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called twidjoy.o. If you want to compile it as a
+	  The module will be called twidjoy. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_DB9
@@ -238,7 +238,7 @@ config JOYSTICK_DB9
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called db9.o. If you want to compile it as a
+	  The module will be called db9. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_GAMECON
@@ -254,7 +254,7 @@ config JOYSTICK_GAMECON
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gamecon.o. If you want to compile it as a
+	  The module will be called gamecon. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_TURBOGRAFX
@@ -268,7 +268,7 @@ config JOYSTICK_TURBOGRAFX
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called turbografx.o. If you want to compile it
+	  The module will be called turbografx. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_AMIGA
@@ -280,7 +280,7 @@ config JOYSTICK_AMIGA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called amijoy.o. If you want to compile it as
+	  The module will be called amijoy. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_JOYDUMP
@@ -293,6 +293,6 @@ config INPUT_JOYDUMP
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called joydump.o. If you want to compile it as
+	  The module will be called joydump. If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 

drivers/input/joystick/iforce/Kconfig

@@ -11,7 +11,7 @@ config JOYSTICK_IFORCE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called iforce.o. If you want to compile it as a
+	  The module will be called iforce. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config JOYSTICK_IFORCE_USB

drivers/input/keyboard/Kconfig

@@ -25,7 +25,7 @@ config KEYBOARD_ATKBD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called atkbd.o. If you want to compile it as a
+	  The module will be called atkbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config KEYBOARD_SUNKBD
@@ -38,7 +38,7 @@ config KEYBOARD_SUNKBD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sunkbd.o. If you want to compile it as a
+	  The module will be called sunkbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config KEYBOARD_XTKBD
@@ -52,7 +52,7 @@ config KEYBOARD_XTKBD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called xtkbd.o. If you want to compile it as a
+	  The module will be called xtkbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config KEYBOARD_NEWTON
@@ -63,7 +63,7 @@ config KEYBOARD_NEWTON
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called maple_keyb.o. If you want to compile it as a
+	  The module will be called maple_keyb. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config KEYBOARD_MAPLE
@@ -75,7 +75,7 @@ config KEYBOARD_MAPLE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called maple_keyb.o. If you want to compile it as a
+	  The module will be called maple_keyb. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config KEYBOARD_AMIGA
@@ -87,6 +87,6 @@ config KEYBOARD_AMIGA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called amikbd.o. If you want to compile it as a
+	  The module will be called amikbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 

drivers/input/misc/Kconfig

@@ -23,7 +23,7 @@ config INPUT_PCSPKR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called pcspkr.o. If you want to compile it as a
+	  The module will be called pcspkr. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_SPARCSPKR
@@ -37,7 +37,7 @@ config INPUT_SPARCSPKR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called pcspkr.o. If you want to compile it as a
+	  The module will be called pcspkr. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config INPUT_M68K_BEEP
@@ -53,7 +53,7 @@ config INPUT_UINPUT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called uinput.o.  If you want to compile it as a
+	  The module will be called uinput.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.	    
 
 config INPUT_GSC

drivers/input/mouse/Kconfig

@@ -25,7 +25,7 @@ config MOUSE_PS2
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called psmouse.o. If you want to compile it as a
+	  The module will be called psmouse. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config MOUSE_SERIAL
@@ -40,7 +40,7 @@ config MOUSE_SERIAL
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sermouse.o. If you want to compile it as a
+	  The module will be called sermouse. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config MOUSE_INPORT
@@ -52,7 +52,7 @@ config MOUSE_INPORT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called inport.o. If you want to compile it as a
+	  The module will be called inport. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 
 config MOUSE_ATIXL
@@ -70,7 +70,7 @@ config MOUSE_LOGIBM
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called logibm.o. If you want to compile it as a
+	  The module will be called logibm. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 
 config MOUSE_PC110PAD
@@ -82,7 +82,7 @@ config MOUSE_PC110PAD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called pc110pad.o. If you want to compile it as a
+	  The module will be called pc110pad. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 
 config MOUSE_MAPLE
@@ -94,7 +94,7 @@ config MOUSE_MAPLE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called maplemouse.o. If you want to compile it as a
+	  The module will be called maplemouse. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 
 config MOUSE_AMIGA
@@ -106,7 +106,7 @@ config MOUSE_AMIGA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called amimouse.o. If you want to compile it as a
+	  The module will be called amimouse. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 
 config MOUSE_RISCPC
@@ -118,6 +118,6 @@ config MOUSE_RISCPC
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called rpcmouse.o. If you want to compile it as a
+	  The module will be called rpcmouse. If you want to compile it as a
 	  module, say M here and read <file.:Documentation/modules.txt>.
 

drivers/input/serio/Kconfig

@@ -15,7 +15,7 @@ config SERIO
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called serio.o. If you want to compile it
+	  The module will be called serio. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_I8042
@@ -31,7 +31,7 @@ config SERIO_I8042
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called i8042.o. If you want to compile it
+	  The module will be called i8042. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_SERPORT
@@ -48,7 +48,7 @@ config SERIO_SERPORT
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called serport.o. If you want to compile it as a
+	  The module will be called serport. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_CT82C710
@@ -63,7 +63,7 @@ config SERIO_CT82C710
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called ct82c710.o. If you want to compile it as a
+	  The module will be called ct82c710. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_Q40KBD
@@ -83,7 +83,7 @@ config SERIO_PARKBD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called parkbd.o. If you want to compile it as a
+	  The module will be called parkbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_RPCKBD
@@ -96,7 +96,7 @@ config SERIO_RPCKBD
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called rpckbd.o. If you want to compile it as a
+	  The module will be called rpckbd. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config SERIO_AMBAKMI

drivers/input/touchscreen/Kconfig

@@ -20,7 +20,7 @@ config TOUCHSCREEN_BITSY
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gunze.o. If you want to compile it as a
+	  The module will be called gunze. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config TOUCHSCREEN_GUNZE
@@ -34,6 +34,6 @@ config TOUCHSCREEN_GUNZE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called gunze.o. If you want to compile it as a
+	  The module will be called gunze. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 

drivers/isdn/hysdn/Kconfig

@@ -6,7 +6,7 @@ config HYSDN
 	depends on m && PROC_FS
 	help
 	  Say Y here if you have one of Hypercope's active PCI ISDN cards
-	  Champ, Ergo and Metro. You will then get a module called hysdn.o.
+	  Champ, Ergo and Metro. You will then get a module called hysdn.
 	  Please read the file <file:Documentation/isdn/README.hysdn> for more
 	  information.
 

drivers/isdn/sc/Kconfig

@@ -9,6 +9,6 @@ config ISDN_DRV_SC
 	  driver currently builds only in a modularized version ( = code which
 	  can be inserted in and removed from the running kernel whenever you
 	  want, details in <file:Documentation/modules.txt>); the module will
-	  be called sc.o.  See <file:Documentation/isdn/README.sc> and
+	  be called sc.  See <file:Documentation/isdn/README.sc> and
 	  <http://www.spellcast.com/> for more information.
 

drivers/md/Kconfig

@@ -41,7 +41,7 @@ config MD_LINEAR
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called linear.o.
+	  will be called linear.
 
 	  If unsure, say Y.
 
@@ -63,7 +63,7 @@ config MD_RAID0
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called raid0.o.
+	  will be called raid0.
 
 	  If unsure, say Y.
 
@@ -85,7 +85,7 @@ config MD_RAID1
 	  learn where to get the supporting user space utilities raidtools.
 
 	  If you want to use such a RAID-1 set, say Y. This code is also
-	  available as a module called raid1.o ( = code which can be inserted
+	  available as a module called raid1 ( = code which can be inserted
 	  in and removed from the running kernel whenever you want).  If you
 	  want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
@@ -110,7 +110,7 @@ config MD_RAID5
 	  learn where to get the supporting user space utilities raidtools.
 
 	  If you want to use such a RAID-4/RAID-5 set, say Y. This code is
-	  also available as a module called raid5.o ( = code which can be
+	  also available as a module called raid5 ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
@@ -141,7 +141,7 @@ config BLK_DEV_DM
 	  Higher level volume managers such as LVM2 use this driver.
 
 	  If you want to compile this as a module, say M here and read 
-	  <file:Documentation/modules.txt>.  The module will be called dm-mod.o.
+	  <file:Documentation/modules.txt>.  The module will be called dm-mod.
 
 	  If unsure, say N.
 

drivers/media/Kconfig

@@ -21,7 +21,7 @@ config VIDEO_DEV
 	  Documentation/video4linux/API.html.  Documentation for V4L2 is
 	  available on the web at http://bytesex.org/v4l/
 
-	  This driver is also available as a module called videodev.o ( = code
+	  This driver is also available as a module called videodev ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.

drivers/media/dvb/frontends/Kconfig

@@ -31,7 +31,7 @@ config DVB_ALPS_TDLB7
 
 	  This tuner module needs some microcode located in a file called 
 	  "Sc_main.mc" in the windows driver. Please pass the module parameter
-	  mcfile="/PATH/FILENAME" when loading alps_tdlb7.o.
+	  mcfile="/PATH/FILENAME" when loading alps_tdlb7.
 
 	  If you don't know what tuner module is soldered on your 
 	  DVB adapter simply enable all supported frontends, the 

drivers/media/radio/Kconfig

@@ -23,7 +23,7 @@ config RADIO_CADET
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-cadet.o.
+	  will be called radio-cadet.
 
 config RADIO_RTRACK
 	tristate "AIMSlab RadioTrack (aka RadioReveal) support"
@@ -51,7 +51,7 @@ config RADIO_RTRACK
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-aimslab.o.
+	  will be called radio-aimslab.
 
 config RADIO_RTRACK_PORT
 	hex "RadioTrack i/o port (0x20f or 0x30f)"
@@ -76,7 +76,7 @@ config RADIO_RTRACK2
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-rtrack2.o.
+	  will be called radio-rtrack2.
 
 config RADIO_RTRACK2_PORT
 	hex "RadioTrack II i/o port (0x20c or 0x30c)"
@@ -101,7 +101,7 @@ config RADIO_AZTECH
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-aztech.o.
+	  will be called radio-aztech.
 
 config RADIO_AZTECH_PORT
 	hex "Aztech/Packard Bell I/O port (0x350 or 0x358)"
@@ -127,7 +127,7 @@ config RADIO_GEMTEK
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-gemtek.o.
+	  will be called radio-gemtek.
 
 config RADIO_GEMTEK_PORT
 	hex "GemTek i/o port (0x20c, 0x30c, 0x24c or 0x34c)"
@@ -153,7 +153,7 @@ config RADIO_GEMTEK_PCI
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-gemtek-pci.o.
+	  will be called radio-gemtek-pci.
 
 config RADIO_MAXIRADIO
 	tristate "Guillemot MAXI Radio FM 2000 radio"
@@ -170,7 +170,7 @@ config RADIO_MAXIRADIO
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-maxiradio.o.
+	  will be called radio-maxiradio.
 
 config RADIO_MAESTRO
 	tristate "Maestro on board radio"
@@ -187,7 +187,7 @@ config RADIO_MAESTRO
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-maestro.o.
+	  will be called radio-maestro.
 
 config RADIO_MIROPCM20
 	tristate "miroSOUND PCM20 radio"
@@ -205,7 +205,7 @@ config RADIO_MIROPCM20
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called miropcm20.o.
+	  will be called miropcm20.
 
 config RADIO_MIROPCM20_RDS
 	tristate "miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)"
@@ -221,7 +221,7 @@ config RADIO_MIROPCM20_RDS
 	  availability of RDS is reported over V4L by the basic driver
 	  already.  Here RDS can be read from files in /dev/v4l/rds.
 
-	  As module the driver will be called miropcm20-rds.o.
+	  As module the driver will be called miropcm20-rds.
 
 config RADIO_SF16FMI
 	tristate "SF16FMI Radio"
@@ -240,7 +240,7 @@ config RADIO_SF16FMI
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-sf16fmi.o.
+	  will be called radio-sf16fmi.
 
 config RADIO_TERRATEC
 	tristate "TerraTec ActiveRadio ISA Standalone"
@@ -263,7 +263,7 @@ config RADIO_TERRATEC
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-terratec.o.
+	  will be called radio-terratec.
 
 config RADIO_TERRATEC_PORT
 	hex "Terratec i/o port (normally 0x590)"
@@ -280,7 +280,7 @@ config RADIO_TRUST
 	  This is a driver for the Trust FM radio cards. Say Y if you have
 	  such a card and want to use it under Linux.
 
-	  This driver is also available as a module called radio-trust.o ( =
+	  This driver is also available as a module called radio-trust ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -308,7 +308,7 @@ config RADIO_TYPHOON
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-typhoon.o.
+	  will be called radio-typhoon.
 
 config RADIO_TYPHOON_PROC_FS
 	bool "Support for /proc/radio-typhoon"
@@ -354,7 +354,7 @@ config RADIO_ZOLTRIX
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called radio-zoltrix.o.
+	  will be called radio-zoltrix.
 
 config RADIO_ZOLTRIX_PORT
 	hex "ZOLTRIX I/O port (0x20c or 0x30c)"

drivers/media/video/Kconfig

@@ -28,7 +28,7 @@ config VIDEO_BT848
 	  If you say Y or M here, you need to say Y or M to "I2C support" and
 	  "I2C bit-banging interfaces" in the character device section.
 
-	  This driver is available as a module called bttv.o ( = code
+	  This driver is available as a module called bttv ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -38,7 +38,7 @@ config VIDEO_PMS
 	depends on VIDEO_DEV
 	help
 	  Say Y if you have such a thing.  This driver is also available as a
-	  module called pms.o ( = code which can be inserted in and removed
+	  module called pms ( = code which can be inserted in and removed
 	  from the running kernel whenever you want).  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
@@ -52,7 +52,7 @@ config VIDEO_PLANB
 	  Otherwise, or if you don't understand a word, say N.
 	  See <http://www.cpu.lu/~mlan/planb.html> for more info.
 
-	  Saying M will compile this driver as a module (planb.o).
+	  Saying M will compile this driver as a module (planb).
 
 config VIDEO_BWQCAM
 	tristate "Quickcam BW Video For Linux"
@@ -61,7 +61,7 @@ config VIDEO_BWQCAM
 	  Say Y have if you the black and white version of the QuickCam
 	  camera. See the next option for the color version.
 
-	  This driver is also available as a module called bw-qcam.o ( = code
+	  This driver is also available as a module called bw-qcam ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -74,7 +74,7 @@ config VIDEO_CQCAM
 	  Connectix QuickCam.  If you have one of these cameras, say Y here,
 	  otherwise say N.  This driver does not work with the original
 	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
-	  as a module (c-qcam.o).
+	  as a module (c-qcam).
 	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
 
 config VIDEO_W9966
@@ -85,7 +85,7 @@ config VIDEO_W9966
 	  Currently tested with the LifeView FlyCam Supra.
 	  If you have one of these cameras, say Y here
 	  otherwise say N.
-	  This driver is also available as a module (w9966.o).
+	  This driver is also available as a module (w9966).
 
 	  Check out <file:Documentation/video4linux/w9966.txt> for more
 	  information.
@@ -103,7 +103,7 @@ config VIDEO_CPIA
 	  Please read <file:Documentation/video4linux/README.cpia> for more
 	  information.
 
-	  This driver is also available as a module (cpia.o).
+	  This driver is also available as a module (cpia).
 
 config VIDEO_CPIA_PP
 	tristate "CPiA Parallel Port Lowlevel Support"
@@ -113,7 +113,7 @@ config VIDEO_CPIA_PP
 	  Vision's CPiA (Colour Processor Interface ASIC), such as the
 	  Creative Webcam II. If you have the parallel port version of one
 	  of these cameras, say Y here, otherwise say N. It is also available
-	  as a module (cpia_pp.o).
+	  as a module (cpia_pp).
 
 config VIDEO_CPIA_USB
 	tristate "CPiA USB Lowlevel Support"
@@ -123,7 +123,7 @@ config VIDEO_CPIA_USB
 	  (Colour Processor Interface ASIC), such as the Creative Webcam II.
 	  If you have the USB version of one of these cameras, say Y here,
 	  otherwise say N. This will not work with the Creative Webcam III.
-	  It is also available as a module (cpia_usb.o).
+	  It is also available as a module (cpia_usb).
 
 config VIDEO_SAA5249
 	tristate "SAA5249 Teletext processor"
@@ -132,7 +132,7 @@ config VIDEO_SAA5249
 	  Support for I2C bus based teletext using the SAA5249 chip. At the
 	  moment this is only useful on some European WinTV cards.
 
-	  This driver is also available as a module called saa5249.o ( = code
+	  This driver is also available as a module called saa5249 ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -197,7 +197,7 @@ config VIDEO_ZR36120
 	  and Buster boards. Please read the material in
 	  <file:Documentation/video4linux/zr36120.txt> for more information.
 
-	  This driver is also available as a module called zr36120.o ( = code
+	  This driver is also available as a module called zr36120 ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -213,7 +213,7 @@ config VIDEO_MEYE
 	  If you say Y or M here, you need to say Y or M to "Sony Programmable
 	  I/O Control Device" in the character device section.
 
-	  This driver is available as a module called meye.o ( = code
+	  This driver is available as a module called meye ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -225,7 +225,7 @@ config VIDEO_SAA7134
 	  This is a video4linux driver for Philips SAA7130/7134 based
 	  TV cards.
 
-	  This driver is available as a module called saa7134.o ( = code
+	  This driver is available as a module called saa7134 ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.

drivers/message/fusion/Kconfig

@@ -21,10 +21,10 @@ config FUSION
 
 	  If you have Fusion MPT hardware and want to use it, you can say
 	  Y or M here to add MPT (base + ScsiHost) drivers.
-	  <Y> = build lib (fusion.o), and link [static] into the kernel [2]
+	  <Y> = build lib (fusion), and link [static] into the kernel [2]
 	  proper
-	  <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
-	  mptscsih.o)
+	  <M> = compiled as [dynamic] modules [3] named: (mptbase,
+	  mptscsih)
 
 	  [2] In order enable capability to boot the linux kernel
 	  natively from a Fusion MPT target device, you MUST
@@ -39,9 +39,9 @@ config FUSION
 
 	  If you say Y or M here you will get a choice of these
 	  additional protocol and support module options:         Module Name:
-	  <M>   Enhanced SCSI error reporting                     (isense.o)
-	  <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
-	  <M>   Fusion MPT LAN driver                             (mptlan.o)
+	  <M>   Enhanced SCSI error reporting                     (isense)
+	  <M>   Fusion MPT misc device (ioctl) driver             (mptctl)
+	  <M>   Fusion MPT LAN driver                             (mptlan)
 
 	  ---
 	  Fusion MPT is trademark of LSI Logic Corporation, and its
@@ -95,7 +95,7 @@ config FUSION_ISENSE
 	  ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
 
 	  Say M for "Enhanced SCSI error reporting" to compile this optional module,
-	  creating a driver named: isense.o.
+	  creating a driver named: isense.
 
 	  NOTE: Support for building this feature into the kernel is not
 	  available, due to kernel size considerations.
@@ -114,7 +114,7 @@ config FUSION_CTL
 	  of the MPT adapter firmware.  Refer to readme file(s) distributed
 	  with the Fusion MPT linux driver for additional details.
 
-	  If enabled by saying M to this, a driver named: mptctl.o
+	  If enabled by saying M to this, a driver named: mptctl
 	  will be compiled.
 
 	  If unsure whether you really want or need this, say N.
@@ -131,7 +131,7 @@ config FUSION_LAN
 	  Installing this driver requires the knowledge to configure and
 	  activate a new network interface, "fc0", using standard Linux tools.
 
-	  If enabled by saying M to this, a driver named: mptlan.o
+	  If enabled by saying M to this, a driver named: mptlan
 	  will be compiled.
 
 	  If unsure whether you really want or need this, say N.

drivers/message/i2o/Kconfig

@@ -22,7 +22,7 @@ config I2O
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  You will get modules called
-	  i2o_core.o and i2o_config.o.
+	  i2o_core and i2o_config.
 
 	  If unsure, say N.
 
@@ -33,7 +33,7 @@ config I2O_PCI
 	  Say Y for support of PCI bus I2O interface adapters. Currently this
 	  is the only variety supported, so you should say Y.
 
-	  This support is also available as a module called i2o_pci.o ( = code
+	  This support is also available as a module called i2o_pci ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -45,7 +45,7 @@ config I2O_BLOCK
 	  Include support for the I2O Block OSM. The Block OSM presents disk
 	  and other structured block devices to the operating system.
 
-	  This support is also available as a module called i2o_block.o ( =
+	  This support is also available as a module called i2o_block ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -58,7 +58,7 @@ config I2O_LAN
 	  support for token ring or FDDI if you wish to use token ring or FDDI
 	  I2O cards with this driver.
 
-	  This support is also available as a module called i2o_lan.o ( = code
+	  This support is also available as a module called i2o_lan ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -71,7 +71,7 @@ config I2O_SCSI
 	  I2O controller. You can use both the SCSI and Block OSM together if
 	  you wish.
 
-	  This support is also available as a module called i2o_scsi.o ( =
+	  This support is also available as a module called i2o_scsi ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -84,7 +84,7 @@ config I2O_PROC
 	  able to read I2O related information from the virtual directory
 	  /proc/i2o.
 
-	  This support is also available as a module called i2o_proc.o ( =
+	  This support is also available as a module called i2o_proc ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.

drivers/mtd/maps/Kconfig

@@ -137,7 +137,7 @@ config MTD_SCx200_DOCFLASH
 
 	  If you don't know what to do here, say N.
 
-	  If compiled as a module, it will be called scx200_docflash.o.
+	  If compiled as a module, it will be called scx200_docflash.
 
 config MTD_L440GX
 	tristate "BIOS flash chip on Intel L440GX boards"

drivers/net/appletalk/Kconfig

@@ -68,7 +68,7 @@ config IPDDP
 	  If you say M here, the AppleTalk-IP support will be compiled as a
 	  module ( = code which can be inserted in and removed from the
 	  running kernel whenever you want, read
-	  <file:Documentation/modules.txt>).  The module is called ipddp.o.
+	  <file:Documentation/modules.txt>).  The module is called ipddp.
 	  In this case, you will be able to use both encapsulation and
 	  decapsulation simultaneously, by loading two copies of the module
 	  and specifying different values for the module option ipddp_mode.

drivers/net/arcnet/Kconfig

@@ -23,7 +23,7 @@ config ARCNET
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called arcnet.o.  If you want to compile it as a
+	  The module will be called arcnet.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -71,7 +71,7 @@ config ARCNET_COM90xx
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called com90xx.o.  If you want to compile it as a
+	  The module will be called com90xx.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -86,7 +86,7 @@ config ARCNET_COM90xxIO
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called com90io.o.  If you want to compile it as a
+	  The module will be called com90io.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -101,7 +101,7 @@ config ARCNET_RIM_I
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you
-	  want). The module will be called arc-rimi.o.  If you want to compile
+	  want). The module will be called arc-rimi.  If you want to compile
 	  it as a module, say M here and read <file:Documentation/modules.txt>
 	  as  well as <file:Documentation/networking/net-modules.txt>.
 
@@ -115,7 +115,7 @@ config ARCNET_COM20020
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called com20020.o.  If you want to compile it as
+	  The module will be called com20020.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt> as
 	  well as <file:Documentation/networking/net-modules.txt>.
 

drivers/net/hamradio/Kconfig

@@ -15,7 +15,7 @@ config MKISS
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called mkiss.o.
+	  will be called mkiss.
 
 config 6PACK
 	tristate "Serial port 6PACK driver"
@@ -35,7 +35,7 @@ config 6PACK
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called 6pack.o.
+	  will be called 6pack.
 
 config BPQETHER
 	tristate "BPQ Ethernet driver"
@@ -64,7 +64,7 @@ config DMASCC
 
 	  This driver can operate multiple boards simultaneously. If you
 	  compile it as a module (by saying M instead of Y), it will be called
-	  dmascc.o. If you don't pass any parameter to the driver, all
+	  dmascc. If you don't pass any parameter to the driver, all
 	  possible I/O addresses are probed. This could irritate other devices
 	  that are currently not in use. You may specify the list of addresses
 	  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
@@ -94,7 +94,7 @@ config SCC
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called scc.o.
+	  will be called scc.
 
 config SCC_DELAY
 	bool "additional delay for PA0HZP OptoSCC compatible boards"
@@ -132,7 +132,7 @@ config BAYCOM_SER_FDX
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  This is
-	  recommended.  The module will be called baycom_ser_fdx.o.
+	  recommended.  The module will be called baycom_ser_fdx.
 
 config BAYCOM_SER_HDX
 	tristate "BAYCOM ser12 halfduplex driver for AX.25"
@@ -151,7 +151,7 @@ config BAYCOM_SER_HDX
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  This is
-	  recommended.  The module will be called baycom_ser_hdx.o.
+	  recommended.  The module will be called baycom_ser_hdx.
 
 config BAYCOM_PAR
 	tristate "BAYCOM picpar and par96 driver for AX.25"
@@ -167,7 +167,7 @@ config BAYCOM_PAR
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  This is
-	  recommended.  The module will be called baycom_par.o.
+	  recommended.  The module will be called baycom_par.
 
 config BAYCOM_EPP
 	tristate "BAYCOM epp driver for AX.25"
@@ -183,7 +183,7 @@ config BAYCOM_EPP
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  This is
-	  recommended.  The module will be called baycom_par.o.
+	  recommended.  The module will be called baycom_par.
 
 config YAM
 	tristate "YAM driver for AX.25"

drivers/net/irda/Kconfig

@@ -9,7 +9,7 @@ config IRTTY_SIR
 	depends on IRDA
 	help
 	  Say Y here if you want to build support for the IrTTY line
-	  discipline.  If you want to compile it as a module (irtty-sir.o), say M
+	  discipline.  If you want to compile it as a module (irtty-sir), say M
 	  here and read <file:Documentation/modules.txt>.  IrTTY makes it
 	  possible to use Linux's own serial driver for all IrDA ports that
 	  are 16550 compatible.  Most IrDA chips are 16550 compatible so you
@@ -72,7 +72,7 @@ config IRTTY_OLD
 	depends on IRDA
 	help
 	  Say Y here if you want to build support for the IrTTY line
-	  discipline.  If you want to compile it as a module (irtty.o), say M
+	  discipline.  If you want to compile it as a module (irtty), say M
 	  here and read <file:Documentation/modules.txt>.  IrTTY makes it
 	  possible to use Linux's own serial driver for all IrDA ports that
 	  are 16550 compatible.  Most IrDA chips are 16550 compatible so you
@@ -86,7 +86,7 @@ config IRPORT_SIR
 	depends on IRDA
 	---help---
 	  Say Y here if you want to build support for the IrPORT IrDA device
-	  driver. If you want to compile it as a module (irport.o), say M here
+	  driver. If you want to compile it as a module (irport), say M here
 	  and read <file:Documentation/modules.txt>.  IrPORT can be used
 	  instead of IrTTY and sometimes this can be better.  One example is
 	  if your IrDA port does not have echo-canceling, which will work OK
@@ -188,7 +188,7 @@ config OLD_BELKIN_DONGLE
 	  Say Y here if you want to build support for the Adaptec Airport 1000
 	  and 2000 dongles.  If you want to compile it as a module, say M here
 	  and read <file:Documentation/modules.txt>.  The module will be
-	  called old_belkin.o.  Some information is contained in the comments
+	  called old_belkin.  Some information is contained in the comments
 	  at the top of <file:drivers/net/irda/old_belkin.c>.
 
 config EP7211_IR
@@ -230,7 +230,7 @@ config USB_IRDA
 	depends on IRDA && USB && EXPERIMENTAL
 	---help---
 	  Say Y here if you want to build support for the USB IrDA FIR Dongle
-	  device driver.  If you want to compile it as a module (irda-usb.o),
+	  device driver.  If you want to compile it as a module (irda-usb),
 	  say M here and read <file:Documentation/modules.txt>.  IrDA-USB
 	  support the various IrDA USB dongles available and most of their
 	  pecularities.  Those dongles plug in the USB port of your computer,
@@ -251,7 +251,7 @@ config NSC_FIR
 
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  nsc-ircc.o.
+	  nsc-ircc.
 
 config WINBOND_FIR
 	tristate "Winbond W83977AF (IR)"
@@ -264,7 +264,7 @@ config WINBOND_FIR
 
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  w83977af_ir.o.
+	  w83977af_ir.
 
 config TOSHIBA_OLD
 	tristate "Toshiba Type-O IR Port (old driver)"
@@ -276,7 +276,7 @@ config TOSHIBA_OLD
 	  maintained and will be removed in favor of the new driver.
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called toshoboe.o.
+	  The module will be called toshoboe.
 
 config TOSHIBA_FIR
 	tristate "Toshiba Type-O IR Port"
@@ -287,7 +287,7 @@ config TOSHIBA_FIR
 	  Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
-	  The module will be called donauboe.o.
+	  The module will be called donauboe.
 
 config SMC_IRCC_FIR
 	tristate "SMC IrCC (EXPERIMENTAL)"
@@ -297,7 +297,7 @@ config SMC_IRCC_FIR
 	  Communications Controller.  It is used in the Fujitsu Lifebook 635t
 	  and Sony PCG-505TX.  If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.  The module will be
-	  called smc-ircc.o.
+	  called smc-ircc.
 
 config ALI_FIR
 	tristate "ALi M5123 FIR (EXPERIMENTAL)"
@@ -310,7 +310,7 @@ config ALI_FIR
 
 	  If you want to compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  ali-ircc.o.
+	  ali-ircc.
 
 config VLSI_FIR
 	tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
@@ -322,7 +322,8 @@ config VLSI_FIR
 	  FIR (4Mbps) speeds.
 
 	  If you want to compile it as a module, say M here and read
-	  <file:Documentation/modules.txt>. The module will be called vlsi_ir.o.
+	  <file:Documentation/modules.txt>. The module will be called
+	  vlsi_ir.
 
 config SA1100_FIR
 	tristate "SA1100 Internal IR"

drivers/net/pcmcia/Kconfig

@@ -30,7 +30,7 @@ config PCMCIA_3C589
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called 3c589_cs.o.  If you want to compile it as
+	  The module will be called 3c589_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>. If
 	  unsure, say N.
 
@@ -43,7 +43,7 @@ config PCMCIA_3C574
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called 3c574_cs.o.  If you want to compile it as
+	  The module will be called 3c574_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.  If
 	  unsure, say N.
 
@@ -56,7 +56,7 @@ config PCMCIA_FMVJ18X
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called fmvj18x_cs.o.  If you want to compile it
+	  The module will be called fmvj18x_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 
@@ -69,7 +69,7 @@ config PCMCIA_PCNET
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called pcnet_cs.o.  If you want to compile it as
+	  The module will be called pcnet_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>. If
 	  unsure, say N.
 
@@ -82,7 +82,7 @@ config PCMCIA_NMCLAN
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called nmclan_cs.o.  If you want to compile it as
+	  The module will be called nmclan_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.  If
 	  unsure, say N.
 
@@ -95,7 +95,7 @@ config PCMCIA_SMC91C92
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called smc91c92_cs.o.  If you want to compile it
+	  The module will be called smc91c92_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 
@@ -108,7 +108,7 @@ config PCMCIA_XIRC2PS
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called xirc2ps_cs.o.  If you want to compile it
+	  The module will be called xirc2ps_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 
@@ -123,7 +123,7 @@ config PCMCIA_AXNET
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called axnet_cs.o.  If you want to compile it as
+	  The module will be called axnet_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.  If
 	  unsure, say N.
 
@@ -136,7 +136,7 @@ config ARCNET_COM20020_CS
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called com20020_cs.o.  If you want to compile it
+	  The module will be called com20020_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 
@@ -150,7 +150,7 @@ config PCMCIA_IBMTR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called ibmtr_cs.o.  If you want to compile it as
+	  The module will be called ibmtr_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 
 config NET_PCMCIA_RADIO
@@ -177,7 +177,7 @@ config PCMCIA_RAYCS
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called ray_cs.o.  If you want to compile it as a
+	  The module will be called ray_cs.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.  If
 	  unsure, say N.
 
@@ -191,7 +191,7 @@ config AIRONET4500_CS
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called aironet4500_cs.o. If you want to
+	  The module will be called aironet4500_cs. If you want to
 	  compile it as a module, say M here and read
 	  <file:Documentation/modules.txt>.
 

drivers/net/tokenring/Kconfig

@@ -32,7 +32,7 @@ config IBMTR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called ibmtr.o. If you want to compile it as a
+	  The module will be called ibmtr. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config IBMOL
@@ -48,7 +48,7 @@ config IBMOL
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called olympic.o. If you want to compile it
+	  The module will be called olympic. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 	  Also read <file:Documentation/networking/olympic.txt> or check the
@@ -66,7 +66,7 @@ config IBMLS
 
 	  This driver is also available as a modules ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The modules will be called lanstreamer.o. If you want to compile it
+	  The modules will be called lanstreamer. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config 3C359
@@ -82,7 +82,7 @@ config 3C359
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will will be called 3c359.o. If you want to compile it
+	  The module will will be called 3c359. If you want to compile it
 	  as a module, say M here and read Documentation/modules.txt.
 
 	  Also read the file <file:Documentation/networking/3c359.txt> or check the 
@@ -111,7 +111,7 @@ config TMS380TR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tms380tr.o. If you want to compile it
+	  The module will be called tms380tr. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config TMSPCI
@@ -128,7 +128,7 @@ config TMSPCI
 
 	  This driver is available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tmspci.o. If you want to compile it
+	  The module will be called tmspci. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config TMSISA
@@ -142,7 +142,7 @@ config TMSISA
 
 	  This driver is available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tmsisa.o. If you want to compile it
+	  The module will be called tmsisa. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config ABYSS
@@ -154,7 +154,7 @@ config ABYSS
 
 	  This driver is available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called abyss.o. If you want to compile it
+	  The module will be called abyss. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config MADGEMC
@@ -166,7 +166,7 @@ config MADGEMC
 
 	  This driver is available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called madgemc.o. If you want to compile it
+	  The module will be called madgemc. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config SMCTR
@@ -184,7 +184,7 @@ config SMCTR
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called smctr.o. If you want to compile it
+	  The module will be called smctr. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 endmenu

drivers/net/tulip/Kconfig

@@ -27,7 +27,7 @@ config DE2104X
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tulip.o.  If you want to compile it as a
+	  The module will be called tulip.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -48,7 +48,7 @@ config TULIP
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called tulip.o.  If you want to compile it as a
+	  The module will be called tulip.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -86,7 +86,7 @@ config DE4X5
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called de4x5.o.  If you want to compile it as a
+	  The module will be called de4x5.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -110,7 +110,7 @@ config DM9102
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called dmfe.o.  If you want to compile it as a
+	  The module will be called dmfe.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -125,7 +125,7 @@ config PCMCIA_XIRCOM
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called xircom_cb.o.  If you want to compile
+	  The module will be called xircom_cb.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>. If unsure, say N.
 
@@ -140,7 +140,7 @@ config PCMCIA_XIRTULIP
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called xircom_tulip_cb.o.  If you want to compile
+	  The module will be called xircom_tulip_cb.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>. If unsure, say N.
 

drivers/net/wan/Kconfig

@@ -54,7 +54,7 @@ config COSA
 
 	  The driver will be compiled as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cosa.o. For general information about
+	  The module will be called cosa. For general information about
 	  modules read <file:Documentation/modules.txt>.
 
 #
@@ -76,7 +76,7 @@ config COMX
 	  use this driver.
 
 	  If you want to compile this as a module, say M and read
-	  <file:Documentation/modules.txt>.  The module will be called comx.o.
+	  <file:Documentation/modules.txt>.  The module will be called comx.
 
 config COMX_HW_COMX
 	tristate "Support for COMX/CMX/HiCOMX boards"
@@ -90,7 +90,7 @@ config COMX_HW_COMX
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  comx-hw-comx.o.
+	  comx-hw-comx.
 
 config COMX_HW_LOCOMX
 	tristate "Support for LoCOMX board"
@@ -101,7 +101,7 @@ config COMX_HW_LOCOMX
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  comx-hw-locomx.o.
+	  comx-hw-locomx.
 
 config COMX_HW_MIXCOM
 	tristate "Support for MixCOM board"
@@ -119,7 +119,7 @@ config COMX_HW_MIXCOM
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>. The module will be called
-	  comx-hw-mixcom.o.
+	  comx-hw-mixcom.
 
 config COMX_HW_MUNICH
 	tristate "Support for MUNICH based boards: SliceCOM, PCICOM (WelCOM)"
@@ -130,7 +130,7 @@ config COMX_HW_MUNICH
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called comx-hw-munich.o. If you want to compile it
+	  The module will be called comx-hw-munich. If you want to compile it
 	  as a module, say M here and read Documentation/modules.txt.
 
 	  Read linux/Documentation/networking/slicecom.txt for help on
@@ -147,7 +147,7 @@ config COMX_PROTO_PPP
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  comx-proto-ppp.o.
+	  comx-proto-ppp.
 
 config COMX_PROTO_LAPB
 	tristate "Support for LAPB protocol on MultiGate boards"
@@ -158,7 +158,7 @@ config COMX_PROTO_LAPB
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  comx-proto-lapb.o.
+	  comx-proto-lapb.
 
 config COMX_PROTO_FR
 	tristate "Support for Frame Relay on MultiGate boards"
@@ -169,7 +169,7 @@ config COMX_PROTO_FR
 
 	  If you want to compile this as a module, say M and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  comx-proto-fr.o.
+	  comx-proto-fr.
 
 #
 # The Etinc driver has not been tested as non-modular yet.
@@ -185,7 +185,7 @@ config DSCC4
 
 	  The driver will be compiled as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called dscc4.o. For general information about
+	  The module will be called dscc4. For general information about
 	  modules read <file:Documentation/modules.txt>.
 
 #
@@ -214,7 +214,7 @@ config LANMEDIA
 	  To change setting such as syncPPP vs cisco HDLC or clock source you
 	  will need lmcctl.  It is available at <ftp://ftp.lanmedia.com/>.
 
-	  This code is also available as a module called lmc.o ( = code
+	  This code is also available as a module called lmc ( = code
 	  which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -229,7 +229,7 @@ config SEALEVEL_4021
 	  This driver can only be compiled as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
 	  If you want to do that, say M here. The module will be called
-	  sealevel.o.
+	  sealevel.
 
 config SYNCLINK_SYNCPPP
 	tristate "SyncLink HDLC/SYNCPPP support"
@@ -317,7 +317,7 @@ config PC300
 	  If you want to compile this as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read Documentation/modules.txt. The module will be
-	  called pc300.o.
+	  called pc300.
 
 	  If you haven't heard about it, it's safe to say N.
 
@@ -369,7 +369,7 @@ config FARSYNC
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want)
 	  say M here and read <file:Documentation/modules.txt>.
-	  The module will be called farsync.o and if you want the module to be
+	  The module will be called farsync and if you want the module to be
 	  automatically loaded when the interface is referenced then you
 	  should add "alias hdlcX farsync" to /etc/modules.conf for each
 	  interface, where X is 0, 1, 2, ...
@@ -408,7 +408,7 @@ config DLCI
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called dlci.o. If you want to compile it as a
+	  The module will be called dlci. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 config DLCI_COUNT
@@ -441,7 +441,7 @@ config SDLA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called sdla.o. If you want to compile it as a
+	  The module will be called sdla. If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt>.
 
 # Wan router core.
@@ -491,7 +491,7 @@ config VENDOR_SANGOMA
 
 	  The driver will be compiled as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called wanpipe.o.  For general information about
+	  The module will be called wanpipe.  For general information about
 	  modules read <file:Documentation/modules.txt>.
 
 config WANPIPE_CHDLC
@@ -583,7 +583,7 @@ config CYCLADES_SYNC
 
 	  The driver will be compiled as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called cyclomx.o. For general information about
+	  The module will be called cyclomx. For general information about
 	  modules read <file:Documentation/modules.txt>.
 
 config CYCLOMX_X25
@@ -610,7 +610,7 @@ config LAPBETHER
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called lapbether.o.  If unsure, say N.
+	  will be called lapbether.  If unsure, say N.
 
 config X25_ASY
 	tristate "X.25 async driver (EXPERIMENTAL)"
@@ -625,7 +625,7 @@ config X25_ASY
 	  If you want to compile this driver as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want),
 	  say M here and read <file:Documentation/modules.txt>.  The module
-	  will be called x25_asy.o.  If unsure, say N.
+	  will be called x25_asy.  If unsure, say N.
 
 config SBNI
 	tristate "Granch SBNI12 Leased Line adapter support"
@@ -634,7 +634,7 @@ config SBNI
 	  This is a driver for ISA SBNI12-xx cards which are low cost
 	  alternatives to leased line modems. Say Y if you want to insert
 	  the driver into the kernel or say M to compile it as a module (the
-	  module will be called sbni.o).
+	  module will be called sbni).
 
 	  You can find more information and last versions of drivers and
 	  utilities at <http://www.granch.ru/>. If you have any question you

drivers/net/wireless/Kconfig

@@ -31,7 +31,7 @@ config WAVELAN
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called wavelan.o.  If you want to compile it as a
+	  The module will be called wavelan.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/modules.txt> as well
 	  as <file:Documentation/networking/net-modules.txt>.
 
@@ -50,7 +50,7 @@ config AIRO
 	  and Cisco proprietary API, so both the Linux Wireless Tools and the
 	  Cisco Linux utilities can be used to configure the card.
 
-	  The driver can be compiled as a module and will be named "airo.o".
+	  The driver can be compiled as a module and will be named "airo".
 
 config HERMES
 	tristate "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)"
@@ -121,7 +121,7 @@ config PCMCIA_NETWAVE
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called netwave_cs.o.  If you want to compile it
+	  The module will be called netwave_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 
@@ -135,7 +135,7 @@ config PCMCIA_WAVELAN
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called wavelan_cs.o.  If you want to compile it
+	  The module will be called wavelan_cs.  If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 

drivers/parport/Kconfig

@@ -28,7 +28,7 @@ config PARPORT
 	  ( = code which can be inserted in and removed from the running
 	  kernel whenever you want), say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  parport.o.  If you have more than one parallel port and want to
+	  parport.  If you have more than one parallel port and want to
 	  specify which port and IRQ to be used by this driver at module load
 	  time, take a look at <file:Documentation/parport.txt>.
 
@@ -47,7 +47,7 @@ config PARPORT_PC
 	  as a module ( = code which can be inserted in and removed from the
 	  running kernel whenever you want), say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  parport_pc.o.
+	  parport_pc.
 
 	  If unsure, say Y.
 
@@ -63,7 +63,7 @@ config PARPORT_SERIAL
 	help
 	  This adds support for multi-IO PCI cards that have parallel and
 	  serial ports.  You should say Y or M here.  If you say M, the module
-	  will be called parport_serial.o.
+	  will be called parport_serial.
 
 config PARPORT_PC_FIFO
 	bool "Use FIFO/DMA if available (EXPERIMENTAL)"
@@ -103,7 +103,7 @@ config PARPORT_AMIGA
 	help
 	  Say Y here if you need support for the parallel port hardware on
 	  Amiga machines. This code is also available as a module (say M),
-	  called parport_amiga.o. If in doubt, saying N is the safe plan.
+	  called parport_amiga. If in doubt, saying N is the safe plan.
 
 config PARPORT_MFC3
 	tristate "Multiface III parallel port"
@@ -111,7 +111,7 @@ config PARPORT_MFC3
 	help
 	  Say Y here if you need parallel port support for the MFC3 card.
 	  This code is also available as a module (say M), called
-	  parport_mfc3.o. If in doubt, saying N is the safe plan.
+	  parport_mfc3. If in doubt, saying N is the safe plan.
 
 config PARPORT_ATARI
 	tristate "Atari hardware"
@@ -119,7 +119,7 @@ config PARPORT_ATARI
 	help
 	  Say Y here if you need support for the parallel port hardware on
 	  Atari machines. This code is also available as a module (say M),
-	  called parport_atari.o. If in doubt, saying N is the safe plan.
+	  called parport_atari. If in doubt, saying N is the safe plan.
 
 config PARPORT_GSC
 	tristate

drivers/pcmcia/Kconfig

@@ -25,8 +25,8 @@ config PCMCIA
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  When compiled this way, there will be modules called pcmcia_core.o
-	  and ds.o.  If you want to compile it as a module, say M here and
+	  When compiled this way, there will be modules called pcmcia_core
+	  and ds.  If you want to compile it as a module, say M here and
 	  read <file:Documentation/modules.txt>.
 
 config CARDBUS

drivers/pnp/Kconfig

@@ -56,7 +56,7 @@ config ISAPNP
 	  Say Y here if you would like support for ISA Plug and Play devices.
 	  Some information is in <file:Documentation/isapnp.txt>.
 
-	  This support is also available as a module called isapnp.o ( =
+	  This support is also available as a module called isapnp ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.

drivers/scsi/aic7xxx/Kconfig.aic7xxx

@@ -13,7 +13,7 @@ config SCSI_AIC7XXX
 	If you want to compile the driver as a module ( = code which can be
 	inserted in and removed from the running kernel whenever you want),
 	say M here and read <file:Documentation/modules.txt>.  The module
-	will be called aic7xxx.o.
+	will be called aic7xxx.
 
 config AIC7XXX_CMDS_PER_DEVICE
 	int "Maximum number of TCQ commands per device"

drivers/scsi/pcmcia/Kconfig

@@ -23,7 +23,7 @@ config PCMCIA_AHA152X
 	  Say Y here if you intend to attach this type of PCMCIA SCSI host
 	  adapter to your computer.
 
-	  This driver is also available as a module called aha152x_cs.o ( =
+	  This driver is also available as a module called aha152x_cs ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -35,7 +35,7 @@ config PCMCIA_FDOMAIN
 	  Say Y here if you intend to attach this type of PCMCIA SCSI host
 	  adapter to your computer.
 
-	  This driver is also available as a module called fdomain_cs.o ( =
+	  This driver is also available as a module called fdomain_cs ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want).  If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -48,7 +48,7 @@ config PCMCIA_NINJA_SCSI
 	  your computer, say Y here and read
 	  <file:Documentation/scsi/NinjaSCSI.txt>.
 
-	  This driver is also available as a module called nsp_cs.o ( =
+	  This driver is also available as a module called nsp_cs ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want). If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.
@@ -60,7 +60,7 @@ config PCMCIA_QLOGIC
 	  Say Y here if you intend to attach this type of PCMCIA SCSI host
 	  adapter to your computer.
 
-	  This driver is also available as a module called qlogic_cs.o ( =
+	  This driver is also available as a module called qlogic_cs ( =
 	  code which can be inserted in and removed from the running kernel
 	  whenever you want).  If you want to compile it as a module, say M
 	  here and read <file:Documentation/modules.txt>.

drivers/serial/Kconfig

@@ -23,7 +23,7 @@ config SERIAL_8250
 
 	  If you want to compile this driver as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  serial.o.
+	  serial.
 	  [WARNING: Do not compile this driver as a module if you are using
 	  non-standard serial ports, since the configuration information will
 	  be lost when the driver is unloaded.  This limitation may be lifted
@@ -73,7 +73,7 @@ config SERIAL_8250_CS
 
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called serial_cs.o.  If you want to compile it as
+	  The module will be called serial_cs.  If you want to compile it as
 	  a module, say M here and read <file:Documentation/modules.txt>.
 	  If unsure, say N.
 

drivers/telephony/Kconfig

@@ -16,7 +16,7 @@ config PHONE
 	  This support is also available as a module.  If you want to compile
 	  it as a module, say M here and read
 	  <file:Documentation/modules.txt>.  The module will be called
-	  phonedev.o.
+	  phonedev.
 
 config PHONE_IXJ
 	tristate "QuickNet Internet LineJack/PhoneJack support"
@@ -25,7 +25,7 @@ config PHONE_IXJ
 	  Say M if you have a telephony card manufactured by Quicknet
 	  Technologies, Inc.  These include the Internet PhoneJACK and
 	  Internet LineJACK Telephony Cards. You will get a module called
-	  ixj.o.
+	  ixj.
 
 	  For the ISA versions of these products, you can configure the
 	  cards using the isapnp tools (pnpdump/isapnp) or you can use the

drivers/usb/storage/Kconfig

@@ -16,7 +16,7 @@ config USB_STORAGE
 
 	  This code is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
-	  The module will be called usb-storage.o. If you want to compile it
+	  The module will be called usb-storage. If you want to compile it
 	  as a module, say M here and read <file:Documentation/modules.txt>.
 
 config USB_STORAGE_DEBUG